VMWare Fusion and network bridging
I’ve had VMWare Fusion running an image of my work laptop, on my Macbook, for nearly three weeks now. I’ve had no problems at all, running over both NAT and via network bridge.
Until this week.
Now, when I try to use the image over network bridge I get the error “The network bridge on device /dev/vmnet0 is not running”. It still works over NAT but i’m perplexed as to where this problem has come from. No software updates, no network config changes, nothing that I can think would affect this at all.
I started to wonder if it was something to do with being assigned a bridged DHCP on my home lan (10.0.0.X), suspending and being brought up on the work lan under a different subnet completely. Maybe something was going majorly wrong with the bridge device.
I couldn’t/can’t find anything logged anywhere other than the error message above in the vmware.log within the VM image folder.
Running the following command restarts all the vmnet related services:
/Library/Application Support/VMWare Fusion/boot.sh –restart
You’ll need to sudo that command.
I haven’t found anything on the VMWare community forums to indicate that this has been bugged for fix in a later release so i’m still not entirely sure of the cause…
Technorati Tags: VMWare Fusion, Networking, OS X, Virtualisation
You can also subscribe via FeedBurner and receive my latest posts by email. If you prefer to use an RSS reader, you can subscribe using this link.
Thank you, this worked for me too. Wonder why vmware can’t do it himself. Sometimes it looks somewhat stupid.
I was going to log this with VMWare but haven’t been able to reproduce it since.
[...] /23.02.2008: Another failure, this entry helped I use now wo different network configurations in Leopard: one server based with a [...]
i would be very grateful if someone could write out in full what i should enter at the prompt in TERMINAL.
no sudo experience, but getting this problem in 1.1.1
thanks,
yossi
Yossi,
No problems:
1. Shutdown VMWare if it is running.
2. Open terminal.
3. Enter the following line exactly (this must be entered all on one line in terminal):
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
4. You’ll be prompted for the Administrator password for your Mac - this is usually the first account that was created when you installed OS X.
5. You’ll see output in terminal as VMWare processes are stopped and then started again, along with the virtual interfaces being assigned their IPs.
Hope that helps, please let me know.
Ian
I have tried the boot.sh restart but still get the problem
Was working fine for me until recently too….
@Mark Wilson - Does the reset complete successfully, as in all the services restart without error?
Does it not fix it at all?
If not, you could try removing the virtual interface from the VM. Then running the boot.sh -restart and then add an interface back in, that might kick it too life.
Finally, search spotlight for ‘vmare.log’ and see if there are any obvious errors in that.
Feel free to post them up here - the errors that is, not the entire log
I tried the fix above and didn’t have any luck. Then I remembered the problem appeared about the same time I tried using two virtual processors. I shut down the virtual machine, switched back to one virtual processor, and switched over to “bridged” from “NAT” again. Seems to work, so far. But it could be coincidence; I can’t be sure of the timing or other changes I made.
I need the bridged mode because with NAT, our HP OfficeJet 7210 scanner won’t communicate with the virtual windows XP machine.
Sorry to say the virtual processor switch appears to have made no difference - the problem still recurs at random intervals.
@Tim Jervis - I’ve not suffered this for almost a month now so i’ve not been able to pin point a root cause nor do any further investigation..
If you get this again, try shutting down the VM and enable diagnostic logging. This will burn CPU time so don’t leave it on for long, just start the VM up long enough to get the error pop up so you capture the trace.
There might be something in there indicating a locked file or process.
[...] on the VMWare Fusion. I tried disabling / enabling network to no avail. Luckily I found this blog post which showed me the steps to restart vm. It fixed my problem [...]
Thanks, this fixed my problem right away.
There’s a bug filed for this now. (I filed it.)
No, don’t ask me anything, I’m not in Fusion engineering.
Worked for me. Thanks!
Once again, thank you for putting this out there! You have saved me much pain and suffering.
Thnx.
Worked like a charm
Worked for me… I had to restart my Mac after doing the steps in Macca’s post but worked great
Thanks! Got me running again.