I have the same problem here, except it only happens if I start VMWare after connecting to a SMB network share from finder go > connect to server.
If I start VMWare before connecting to the smb resource the VM starts fine, however I then cannot connect to SMB from finder at all and just get a generic couldn't connect to server.
This means it is now not possible for me to mount the vm Windows drive over the network from the host mac which is a big problem.
I also have VirtualBox installed but don't believe this is a problem. I also have MySQL installed which causes the mac to hang on shutdown but I don't believe this is related.
more info on the subject and why you are bumping into the problem is here:
Note that in some cases just restarting the host OS is sufficient, but if you are really running out of major device numbers then just a reboot might not be enough to fix it.
Wil| Author of Vimalin. The virtual machine Backup app for VMware Desktop Products
| Vimalin : Automated backups for VMware Fusion and VMware Workstation Professional
| More info at https://www.vimalin.com
| Twitter @wilva
| VMware Wiki at http://www.vi-toolkit.com
After uninstalling VirtualBox, my VMs in Fusion seem to boot up fine.
What I don't understand is that both used to work prior to updating to macOS 10.12.
Same boat here. Both VMware and VirtualBox installed. Both worked fine before macOS Sierra. After updated to Sierra, I get the same error message trying to open a VMware VM. Uninstalling VirtualBox and re-installing VMware fixed the issue but ultimately I need VirtualBox as well for various things.
Edit: tried to re-install VirtualBox after I got everything working again with VMware 7.1.3, and it seems VirtualBox will not install in macOS Sierra. So maybe this is more related to VirtualBox than VMware(?):
Edit #2: after further experimentation it seems like VirtualBox does work fine on macOS Sierra, but requires fully uninstalling VMware Fusion in order to successfully install VirtualBox.
Same issue here - Fusion and VirtualBox seem to no longer co-exist since Sierra
I confirm uninstalling VirtualBox fixed the issue.
Don't know whats happening but since I payed for Vmware Fusion and not VirtualBox I expect better support here
This is a weird one... In previous versions of OS X this was never an issue. We're investigating why this is happening with macOS, and we'll likely be working directly with Apple to produce a fix.
I confirm, uninstall Virtual Box solve the issue.
I found a script to uninstall easily it osx - Yosemite + Fusion 7.0.1 now gets "Could not open /dev/vmmon: No such file or directory." and will not start any VM…
This script that you recommended is EXACTLY what worked!!
To make it easier for others:
- Download VirtualBox_Uninstall.tool
- Open the Terminal
- Browse to the directory where you downloaded it
- Run it with
sudo sh VirtualBox_Uninstall.tool
run the script above and remove virtual box, worked straight away for me, many thanks
Has the resolution to this issue progressed any?
I'm using the same environment as original post and require both VMWare and Virtualbox machines (via Vagrant) for my development and support role.
Manually uninstalling these products each time I need to bring a VM up (vagrant up) is less than convenient.
Please any advice on having these products cohabit the same MacOS would be great.
Thanks in advance.
I'm NOT using VirtualBox. I'm running VMware Fusion 6.0.4 under Mac OS-X Sierra 10.12.3 and started seeing this /dev/vmmon error a couple of months ago. None of the suggested fixes I've seen so far seem appropriate. I'll need this fixed pretty soon as I have to analyze data for an experiment at J-PARC in Japan and another at TRIUMF in Vancouver, and my only (previously) working installation of the required software is on my Mac's VMware Ubuntu installation.
Any suggestions? HELP!
just to add, it seems fusion 6 supported up to maverick only
so I installed fusion 8.5 and no problem with /dev/vmmon