An ugly VMWare Fusion error “/dev/vmnet0” is not running
A VMWare Fusion getcha (new word?) that I ran into tonight. So you don’t waste much time with it, here’s how to fix it. Don’t panic if you encounter an “the network bridge device on /dev/vmnet0
is not running” when trying to start your VMWare instance. It generally means a service didn’t start correctly when you booted your machine.
You can check if its running by running the following command:
# sudo /Library/Application\ Support/VMware\ Fusion/vmnet-cli --status |
Don’t suspend your VM. Let your VM start. Go to a full screen view and shutdown the machine without logging on to a running instance. Shutdown VMWare Fusion. Now, you can reboot your Mac or you can run the following command from the /Library/Application Support/VMWare Fusion
directory (options are --start
, --stop
, or --restart
):
# sudo ./boot.sh --restart |
Alternatively, you can run the command like this from any directory.
# sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart |
After restarting the service, you shouldn’t have any problem launching VMWare Fusion. I don’t like the fact that you can’t abort the launch of the VM though. That’s got to be a bug!.