After I update to Mac OS X Yosemite, I failed to open VMware Fusion 5, it shows
- Could not open /dev/vmmon: No such file or directory.
- Failed to initialize monitor device.
- Cannot find a valid peer to process to connect to.
I tried to uninstall the VMware, restart the Mac, and install the VMware again, but still this problem.
I searched in Google and found another article discussing about this before, the solution is as below:
I can not find the below applications in my Mac, so can not uninstall. Anyone has my issue after upgrade to Yosemite?
- Studio Network Solutions iSCSI initiator
- Viscosity VPN
- VirtualBox
----------------------------------
Looking further back in the support information bundle's history gave me a big clue. It seems that some driver on your system is triggering the problem by consuming all of the available "character device major numbers" (a small number used to identify a driver/device). I can't immediately identify the culprit driver, but the possibilities include:
- Studio Network Solutions iSCSI initiator
- Viscosity VPN
- VirtualBox
We have quite a few users with VirtualBox alongside Fusion, so I doubt that VirtualBox is the cause, or I'd expect to have seen more widespread reports of this problem, unless it's being exacerbated by some other environmental factor.
It's also possible (although less likely) that it is a problem with one of the drivers built in to Mac OS, or it might even be one of the other drivers in VMware Fusion, but – again – in either of those cases I'd expect to have encountered more reports of the problem unless it's triggered by some other factor on your system.
Could you try temporarily uninstalling either the SNS iSCSI initiator or Viscosity VPN and see if that helps?
Cheers,
--
Darius
Fusion 5 - Could not open /dev/vmmon: No such file or directory.
-------------------------------------------------------