I seen some earlier versions were also popping up "Could not open /dev/vmmon: No such file or directory.", with remedies such as:
1. Reinstall VMWare Fusion
2. Repair permissions.
I have reinstalled VM - same problem.
Under macOS Sierra there is no way to repair permissions - option for that has been removed from disk utils and from command line.
It is said VMWare Fusion 8.5 is coming (now delayed) - but till that, what other fix is available?
Thanks!
I had this problem. Now it is working in macOS Sierra 10.12.
It should work after all these steps
The same issue is occurring for me with Mac OS Sierra.
(kernel) Kext com.vmware.kext.vmx86 start failed (result 0x5).
(kernel) Kext com.vmware.kext.vmx86 failed to load (0xdc008017).
(kernel) Failed to load kext com.vmware.kext.vmx86 (error 0xdc008017).
Failed to load ../kexts/vmmon.kext - (libkern/kext) kext (kmod) start/stop routine failed.
Not found a fix so far.
Cheers
Have you tried rebooting the host?
Restarting the host OS, or reinstalling VMWare did not fix the issue for me.
I have tried:
same problem repeats.
It is important to note that VMWAre claims on ints Fusion product page:
www.vmware.com/products/fusion.htmlH
Compost Operating Systems
Tech Specs / Host Systems
Which is not correct - most likely they put it on due to coming 8.5.
I don't suppose this will be of much comfort to you, but I can comment, in passing, that VMware Fusion Pro 8.1.1 is running fine in macOS Sierra Golden Master on my Mac Pro 5,1. No such message as "Could not open /dev/vmmon: No such file or directory" has ever appeared. I wish I could offer further information.
Same issue here - just upgraded from BETA to GM and I get the error starting the very same VM I was running before the upgrade:
default | 15:58:16.987474 +0100 | kernel | Kext com.vmware.kext.vmx86 start failed (result 0x5). |
default | 15:58:16.987483 +0100 | kernel | Kext com.vmware.kext.vmx86 failed to load (0xdc008017). |
default | 15:58:16.987487 +0100 | kernel | Failed to load kext com.vmware.kext.vmx86 (error 0xdc008017). |
default | 15:58:16.993189 +0100 | kextd | Failed to load /Applications/VMware Fusion.app/Contents/Library/kexts/vmmon.kext - (libkern/kext) kext (kmod) start/stop routine failed |
Interestingly I was getting the same errors from Shimo VPN client with the Beta regarding its kexts.
Figure there is something about the kexts that Sierra GM is not liking.
Help!!
Hi,
Upgrade to Fusion 8.5 it just has been released and macOS Sierra is on the list as supported.
VMware Fusion 8.5 Release Notes
--
Wil
We've not seen that error here with 8.1 or 8.5, so please let us know if the issue persists in 8.5. We just released a few minutes ago, so you should be able to just 'check for updates' within the app.
Upgraded to 8.5 but still seeing the error. Here are the two errors I see:
On starting a VM: https://cloudup.com/cat8rprZFpJ
After clicking OK on ^: https://cloudup.com/cWrPs0XNdSB
I'm also seeing the same error if I create a new VM.
I had this problem. Now it is working in macOS Sierra 10.12.
It should work after all these steps
Thanks. That fixed the issue.
I moved from Fusion to VirtualBox and worked fine.
Upgrading to 8.5 did not worked, I needed to clean install and restart machine. Then original problem is finally fixed.
Hovever, new problem begins - drag and drop hangs host machine...
I will consider VirtualBox as future VM solution on my machine.
Most of the issues I had with VMWare (like "Could not open /dev/vmmon: No such file or directory."), were caused by conflicts between VMWare and VirtualBox. When I uninstalled VirtualBox everything started working again.
So I managed to get Fusion 8.5 Pro working on GM with a reinstall....
I then downloaded and installed the GM2 release and the problem came back.
By a strange coincidence Shimo who's kexts were not working with GM now works with GM2
2016-09-17T15:56:58.118Z| VMware Fusion| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket
2016-09-17T15:56:58.118Z| VMware Fusion| I125: SOCKET connect failed, error 2: No such file or directory
2016-09-17T15:58:18.116Z| VMware Fusion| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket
2016-09-17T15:58:18.118Z| VMware Fusion| I125: SOCKET connect failed, error 2: No such file or directory
2016-09-17T16:00:26.147Z| VMware Fusion| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket
2016-09-17T16:00:26.147Z| VMware Fusion| I125: SOCKET connect failed, error 2: No such file or directory
I get No such file or directly error.
Same kext error messages as before:
default | 16:08:05.648077 +0100 | kernel | vmmon: Loaded com.vmware.kext.vmx86 Version 0435.27.17 Build 4352717 (Sep 6 2016 19:44:03) |
default | 16:08:05.648144 +0100 | kernel | vmmon: Warning: Failed to register the major device number. |
default | 16:08:05.648416 +0100 | kernel | Kext com.vmware.kext.vmx86 start failed (result 0x5). |
default | 16:08:05.648419 +0100 | kernel | Kext com.vmware.kext.vmx86 failed to load (0xdc008017). |
default | 16:08:05.648421 +0100 | kernel | Failed to load kext com.vmware.kext.vmx86 (error 0xdc008017). |
default | 16:08:05.030808 +0100 | kextd | Failed to load /Applications/VMware Fusion.app/Contents/Library/kexts/vmmon.kext - (libkern/kext) kext (kmod) start/stop routine failed |
Hi wojciech_czyz
Welcome to VMware Fusion forum.
''Hovever, new problem begins - drag and drop hangs host machine..." could you help provide more info about this issue? Any screenshot or more detailed steps is better. Thanks.
Same here, I uninstalled VirtualBox using CCleaner, and the error went away.