Btw, I've found no setting to switch which network adapter gets bridged...
Also, when you do connect to an airport network, you can repair the connection in XP and it works...
There's no friendly setting, currently, to set which network adapter we bridge to, but it's supposed to automatically follow what the host OS is using for connectivity.
Oh, so I should file a bug for this?
Perhaps it really is a Firewire issue?
Yeah, please file a bug for this. I'm actually not sure we support bridging to firewire.
On the message contents, you're entirely right, but nobody's supposed to see that message. It did tell you what you needed to know -- bridged networking won't work -- though the details on why would be gobbledygook to most people, agreed.
Thank you for the reply.
Sorry to resurrect this old thread, but there seems to be a related issue -- if there are no network connections to the internet available when you start your VM, you're hosed -- you have to shut down and restart it again if you're in bridged mode. I guess it assumes if there are no network connections, then there never will be?
Use case -- my wireless connection sometimes takes around 30 seconds to a minute to reconnect to my wireless AP (via WPA-PSK) after I wake up my laptop. If I start my VM in this time period I never can have network connectivity unless I shut it down (not just restart it).
In Parallels, the virtual network adapter has the ability to find the network -- and I can even repair the connection once my wireless connection gets going.
The Repair Connection is greyed out in this situation in Windows XP under VMware.
BTW, i tried to submit this feedback on the support page this morning, and the page is telling my that I need the 'Account' field filled in(?)
I am seeing this message, and doing a quick ls of /dev doesn't show any such device. Is there supposed to be a /dev/vmnet0 device? When does it get created?
I ran into the same problem twice now. The first time was very annoying because I was on a train and had thus no chance to work properly. It got fixed for now by (re-)installing VMWare (BETA 1.1) on top of my initial installation but it had given me quite a time of cluelessly looking through config files and trying out new settings.
I was trying to get an internal connection in order to mount a network volume and possibly, the requested device was /dev/vmnet1 while the second time, I was connected to the internet via airport and the requested device was /dev/vmnet0.
I occasionally run into this error message, and it used to be the only solution was to restart my Mac. I use an Ethernet cable for my network connection, and it's always connected. For whatever reason though, Fusion will pop up with this error every so often.
Digging around I found this seems to help me with my problem:
1. Open Terminal
2.. Type the following line:
sudo "/Library/Application Support/VMWare Fusion/boot.sh" --restart
3. Type in your password when prompted
4. Close Terminal
Now I can reconnect my virtual machine to the network without having to reboot.
I'm running windows xp in the vm and i just recently upgraded to Leopard and i'm getting that error too...i tried the terminal fix but didn't work for me =( I'm connected via ethernet cable.
I'm running windows xp in the vm and i just recently upgraded to Leopard and i'm getting that error too
Major system changes (e.g. upgrading to Leopard) may require reinstalling Fusion.
When I upgraded to Leopard I got this message using Fusion 1.0. An upgrade to 1.1RC solved it for me (although perhaps reinstalling 1.0 will also do the job).
reinstalling the RC and rebooting Leopard fixed it for me
i installed fusion 1.1 and everything is working as it should