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.
Ron said
I wasn’t successful with the Step by Step approach. I have Fusion 1.1.3 on a MBPro running 10.5.7 When I open Terminal this is displayed
Last login: Sat Feb 28 07:37:49 on console
ron-friedmans-macbook-pro:~ ronfriedman$
I enter sudo/Library/Application\Support/VMware\Fusion/boot.sh –restart When I press return, I get this reply
-bash: sudo/Library/ApplicationSupport/VMwareFusion/boot.sh: No such file or directory
ron-friedmans-macbook-pro:~ ronfriedman$
What am I doing incorrectly?
Michael said
Hello,
did you really enter the caommand like this ? I just tested the command and it’s fine.
check the spaces:
sudo{SPACE}/Library/Application\{SPACE}Support/VMware\{SPACE}Fusion/boot.sh –restart
Regards
Michael
Ron said
Michael,
I re-entered to command and got further this time as I received this reply after hitting return…
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type “man sudo” for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
… When I tried entering my password, nothing happened. The cursor didn’t move; nor did asterisks appear. Then I wondered if I was actually entering the password but it was hidden (for security?) so I tried twice more and received a “3 failed attempts” reply and the original command line information appeared again… see below
Last login: Sat Feb 28 07:37:49 on console
ron-friedmans-macbook-pro:~ ronfriedman$
Thank you and I apologize for taking so much of your time, but do you have another idea about how I sould proceed?
Regards,
Ron
Ryan Corrigal said
I noticed that when I was connected to a VPN, the adapter didn’t work. As soon as I disconnected from the VPN, it worked.
Interesting.
Scott Burton said
Thanks Ryan, I was trying to figure out why I couldn’t fix the bridged network. I can confirm that it doesn’t work while connected to a VPN.
Smated said
What the heck this isn’t working for me… dang it…
ammoun said
Guys,
There is something wrong with the VMware/Win 7 and VMware/Vista (all versions of both software) combo when it comes to networking and the network adapter selection NAT and Bridged.
With the IP setting in my adapter set at automatic as it should be usually, NAT works and I can see the internet but no local network, Bridged sees nothing at all.
However, in Bridged configuration if I set my own IP address, Gateway IP and DNS IP, the “Bridged” network adapter works fine and I can see my network printer (local network) …etc and the internet. This is not true in NAT, it must be left as automatic IP selection and it will not see the local network!!
This is weird and most definitely has to do with the VMware/Win 7 (Vista) combo failing to obtain and IP address (register on the network) properly.
I hope this will help someone temporarily.
What is even more weird is VMware not resolving this issue for two whole years now! Look up this problem and you will see people complaining for two or more years and still are!!! I have VMware 3 and Win 7 and am facing this on a completely fresh Win 7 installation! On my VMware Fusion 2 and Win XP there was no such problems! maybe I ought to go back!!
Any other suggestions from anyone, besides restarting the service using Sudo and Terminal which did not work at all?? I do not wish to keep my IP set as I move from one WiFi network to another at different venues.
Bless you all and thank you for all your efforts.