Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module vmmon

[jwerginz]

Try and open a VM:

Could not open /dev/vmmon: No such file or directory.

Click Ok

Please make sure that the kernel module `vmmon' is loaded.

Click Ok

This just started happening when I try and open a VM from Fusion 8.5.10.  Uninstalling and Re-installing VM Fusion doesn't help.  This is on a Mac (Mojave OS).  Also don't get anything in Security and Privacy in Mac like I have seen on other posts.

[Technogeezer]

If I understand you correctly, are you are trying to use Fusion 8.5.10 on Mojave? If so that's not supported and won't work. You will need Fusion 11 for use on Mojave.

See the VMware KB article Supported host operating systems for VMware Fusion and VMware Fusion Pro (2088571) for the supported Fusion and macOS version matrix. 

[jwerginz]

I upgrade to Mojave at least a year ago with the same version of Fusion.  So not sure what happened between last week and today.  The OS has not changed and neither has the Fusion version.

[jwerginz]

According to the chart it says:  Fusion 11.1.1 and Earlier.  So 8.5.10 should work and again it has for a long time.

[Technogeezer]

The chart does not say that. A “yes” (meaning a supported combination) only appears for Mojave and the Fusion 11 versions.

The “fusion 11.1.1 and earlier refers to Fusion versions, not macOS versions. They make that distinction on Fusion versions because Fusion 11.5  added support for Catalina. 

[jwerginz]

I installed Fusion 11.5.7.  Still cannot access the images.  I get a slightly different error now:

Could not open /dev/vmmon: Broken pipe.  (This is slightly different)

Please make sure that the kernel module `vmmon' is loaded. (This is same)

Failed to initialize monitor device.(This is same)

Transport (VMDB) error -14: Pipe connection has been broken  (This is new)

Nothing in System like before to resolve this issue.

[Technogeezer]

Can you attach a copy of the vmware.log file that's found in the virtual machine's bundle?

[jwerginz]

See attached.

[jwerginz]

Actually that is the last date the image successfully came up looking at the log.  There is nothing since 12/08

[Technogeezer]

The file you uploaded appears to be from December 10th. What's strange is that it indicates that it's running on a PC - with Workstation 17 Player, not VMware Fusion. 

I just want to make sure we're talking about the same VM here - the one that's giving you the errors.

[Technogeezer]

Ah, our replies crossed in the thread. I was confused about what I saw and you explained it, thanks.

[Technogeezer]

Also, what is the Mac model this is running on (from About This Mac)?

[jwerginz]

MacBook Pro (Retina, 15-inch, Late 2013)

[Technogeezer · Accepted solution]

I just remembered something that you might want to check.

There was a similar problem reported and the root cause of that was improper permissions on the /private/var/db/KernelExtensionManagement folder

See the reply in this thread from jameslodberg:

https://communities.vmware.com/t5/VMware-Fusion-Discussions/VM-s-not-working-in-Fusion/m-p/2816692/h...

[jwerginz]

ls -lO /private/var/db/

The restricted flag was off (now on):

drwxr-xr-x@ 3 root wheel restricted 96 Apr 22 2022 KernelExtensionManagement

Not sure how this happened - it works now though - appreciate the back and forth to get this resolved.

[Technogeezer]

Sorry I didn't think of this one sooner, but glad you've gotten it running.

There have been a couple of things going on that have caused some really strange problems for Fusion. This is one, but there's another one that has been seen frequently - something changing the default permissions on /private/var/tmp. It's not clear whether that's the fault of macOS or something running behind the scenes.