I'm using a 13-inch 2012 non-Retina MacBook Pro (MacBookPro9,2). I have VMware Fusion 11.0.1. This is a problem I also experienced on my previous version (I think it was 8.x?).
Whenever I try to open a virtual machine, it throws two errors:
What do these errors mean and how do I fix them?
Accepted Solutions
The error itself means the hypervisor can’t be loaded into memory. vmmon is the actual ‘hypervisor’ part of the hypervisor, and relies on a series of kernel extensions to load properly.
The error indicates that the vmmon kernel extension itself (which we lovingly call ‘the monitor’) is not loading into memory.
This can happen for a few reasons, and the most common today is the security settings that Mojave imposes.
So our team is always going to check that first, please don’t feel belittled by it. We don’t know your technical prowess before asking 
Other times this can happen when upgrading if a KEXT doesn’t unload in time before the new one needs to get loaded when the app launches (we load kexts dynamically and unload them when the app quits). Usually a reboot can fix that, sometimes a re-install is needed.
I’ve also seen weird reports of permissions messing things up, and you have to actually drag the Fusion.app onto the Desktop and then back to /Applications to reset an invalid ACL value.
The error itself means the hypervisor can’t be loaded into memory. vmmon is the actual ‘hypervisor’ part of the hypervisor, and relies on a series of kernel extensions to load properly.
The error indicates that the vmmon kernel extension itself (which we lovingly call ‘the monitor’) is not loading into memory.
This can happen for a few reasons, and the most common today is the security settings that Mojave imposes.
So our team is always going to check that first, please don’t feel belittled by it. We don’t know your technical prowess before asking
Other times this can happen when upgrading if a KEXT doesn’t unload in time before the new one needs to get loaded when the app launches (we load kexts dynamically and unload them when the app quits). Usually a reboot can fix that, sometimes a re-install is needed.
I’ve also seen weird reports of permissions messing things up, and you have to actually drag the Fusion.app onto the Desktop and then back to /Applications to reset an invalid ACL value.