VMware Fusion “The network bridge device on /dev/vmnet0 is not running”
Posted by Michael on January 27, 2008
Suddenly ran into this problem, no vm worked anymore. Searching the internet gave me hints but no solution.
The clue was in the System profiler. I had switched from a server based to a local pppoe connection. This pppoe connection showed in system profiler as another ethernet en0 BSD device name. After deleting and re-creating the pppoe connection on the second internal ethernet en1 everything was ok again !
Nothing perfect yet …
Switching to local pppoe I have to remove the router entry from the network device, but then vm’s don’t work anymore.
But with an router entry internet doesn’t work correct.
I use now wo different network configurations in Leopard: one server based with a router entry and another one with a local pppoe connection.
Edit /23.02.2008: Another failure, this entry helped
Edit /20.04.2008: Every now and then I still get this error. Either this command
sudo /Library/Application Support/VMWare Fusion/boot.sh –restart
or rebooting helps.
macca said
Since upgrading to 1.1.1 last week, I haven’t had this problem again.
However, time sync between the host machine and Windows VM is now broken and the clock has to be reset manually or by net time.
Mikkel said
Actually it should be:
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restartJoseph said
I ran into this today and filed a bug. I don’t know what causes it, and I’m not in Fusion engineering so I can’t answer any questions or provide status. Just thought I’d let you know.
VMWare Fusion Bridged Network Problem « More Soma Please… said
[...] to another WordPresser here for the [...]
OrtoMar said
Have got this error and could resolve it with mentioned command.
A TCP/IP conflict between a second Mac, not the one on which VMWare Fusion is installed and Windows 2000 VMWare Fusion client were the cause of this error. Both were configured as DHCP with variable TCP/IP.
GeroZ said
Short ACK: Yes, this works. Thanks a lot – I usually rebooted the entire Mac to get it working.
notechyet said
Exactly the same error started after I installed Clamxav and I have been able to solve it with the above suggestion:sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
Thanks
David said
Thanks a ton. I suddenly started getting this error this morning and was kinda starting to get worried. This fixed it right up. Thankfully I was able to access the web on the Mac side.
Aaron said
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
I put that in the terminal and my problems were solved. Thanks for the solution!
Aboo said
Solved mine too.
Milton Lopez said
I just started having the same problem with Fusion 2.0 after running fine for a while. I tried the boot.sh script mentioned here, but I get these two errors:
-bash: boot: command not found
boot.sh: Line 753: boot.sh: command not found
Any suggestions?
Chi said
Works!
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
Make sure there’s a — before restart
Works! said
This works:
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
/Sune
jptxs said
this was helpful. thanks. I found it was enough to just run the command from within the script:
sudo /Library/Application\ Support/VMware\ Fusion/vmnet-bridge -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ”
Lespol said
WORK!, Tnxs
Rob said
Yeah, been using this command with 1.0, 1.1 and now 2.0…
Anyone know why I need to issue it a couple times a week? It’s a minor issue now – because I’m used to it, but it’s a huge bug.
Tom said
Just had the same issue with 2.0 and the sudo command helped a lot! I just couldn’t run it like that from the terminal, I had to user@machine:~> sudo su and then sh-3.2# /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
Thanks for the tip, it helped a lot!
VMware Fusion “The network bridge device on /dev/vmnet0 is not running” error - Search & Refactor said
[...] A quick online search revealed me multiple solutions but the most of them were targeting VMware 1.0. The error above in WMvare 2.0 or greater can be easily fixed typing the following command in the Terminal (thanks Aaron). [...]
GeroZ said
I haven’t seen this in a long time, and I’m using VMware Fusion 2 (currently: 2.0.4) productively each and every day. I though that was history since the upgrade from Fusion 1 to 2.
So I was quite baffled seeing it today occur again. However: “[...] boot.sh –-restart” worked for me – thanks again!
Woo said
Thanks the sudo worked great for me. I am curious how you figured out that this would work?
Kevin said
Because it’s what vmware runs when it starts. See here: /Library/LaunchDaemons/com.vmware.launchd.vmware.plist (the launchd script). Good find though!
Phil said
I never had this issue until a couple weeks ago, now I have had to run the script twice to get the network back up. I have a Canon network printer that forces me to run the VM in bridged mode vs. NAT now. This is becoming a real PIA.
Jan said
Have been running Fusion w/out this issue since January, just ran into it today. Did install latest various Apple upgrades from June 5 might be related not sure. Run an iMac 24″ early 2008 4Gb ram. Run this command foudn on this thread fixed issue:
” sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart “
Fred said
This worked for me today running VMWare Fusion 2.0.4
For those who are in need of step by step on a typical Mac:
1) Go to APPLICATIONS folder
2) Select UTILITIES
3) Select TERMINAL.app
ALTERNATE: Type terminal into FINDER or SPOTLIGHT
Copy and paste the following into terminal:
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh –restart
(Make sure there are two hyphens before “restart” if your system made it into one dash;
in other words, the end is /boot.sh followed by a space then two hyphens followed WITHOUT a space by the word restart).
Press RETURN
You may get a warning about using SUDO.
You will have to enter your passwork and press RETURN
Go back to VM Fusion Ware
Under VIRTUAL MACHINE
Go to NETWORK ADAPTER
Click on CONNECT NETWORK ADAPTER if necessary
Finished!
Russ said
Thanks – this annoying error was fixed with the help of the “Step by Step”! I appreciate your comments and have forwarded this to my Mac/Fusion user friends.