VMWare’s Fusion Error Message: The network bridge on device /dev/vmnet0 is not running.
I upgraded to VMFusion 2.0rc1 today (this keeps getting better and better!) After doing so, when I changed the settings for the VM network from NAT to bridged, I got the following:
The network bridge on device /dev/vmnet0 is not running.
After almost switching to Pararllels, I found the solution at Fine Malt Techr.
What you need to do is run the following command from Terminal (it will ask you for a password):
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
The VM can be running while this is going on. Immediately after, I was able to switch to bridged mode and the world was a much better place – at least for me 
Tags: Virtualization
September 5th, 2008 at 11:15 pm
glad to help.
September 7th, 2008 at 4:51 pm
@macca: thank you!
October 30th, 2008 at 12:56 am
Thanks Worked well, though I couldn’t cut and paste from this page for some reason. I just gave me the “usage” message. When I typed it in using tab completion and two hyphens before restart it worked. Not sure why.
BTW, this version of Fusion (besides this glitch) is a big improvement.
Thanks again!
April 1st, 2009 at 12:30 am
thank you
thank you
thank you
April 1st, 2009 at 12:30 am
Oh yah they must have change the syntax. This is what worked for me
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
all one line
May 25th, 2009 at 7:23 am
just use the double dash before the restart parameter as
boot.sh –restart
May 25th, 2009 at 7:24 am
Sorry but the double dash – – is not showing well on the site
May 25th, 2009 at 7:26 am
Sorry but the double dash “–” is not showing well on the site
September 1st, 2009 at 8:53 am
Thanks! This solved my issue when I upgraded to Snow Leopard and I got this error.
September 1st, 2009 at 9:16 am
@Hilyin:
Great to see you got it working.
How is SL treating you? I upgraded back to Leopard, SL was driving me nuts: http://scorpiotek.com/blog/?p=485