VMware Communities
wickedcoyote
Contributor
Contributor
‎05-06-2019 07:45 AM

After upgrade to Mojave fusion 11 errors "Unable to retrieve kernel symbols." & "Failed to initialize monitor device."

Ever since I've upgraded to Mojave on my MID 2012 MBP (i7 2.6 GHZ, 16GB ram, SSD HDD) I cannot run any VM's.  I've tried creating new VM's and still get the same errors.  I have given Fusion Full disk access in security settings and still no joy.

0 Kudos
6 Replies
ColoradoMarmot
Champion
Champion
‎05-06-2019 08:57 AM

Uninstall (drag to trash, reboot, empty trash, and reinstall.  That's likely to fix it.

0 Kudos
wickedcoyote
Contributor
Contributor
‎05-06-2019 09:04 AM

I have tried Uninstalling with removing of library files described in the KB "Manually uninstalling VMware Fusion (1017838)" rebooted and reinstalled with no success.

0 Kudos
bfan
VMware Employee
VMware Employee
‎05-13-2019 12:30 AM

Seems the kernel extension is blocked by OS, could you check option 'App Store and identified developers' is selected in 'Security & Privacy' setting?  if so,  execute command 'kextstat | grep vm' in terminal to see what kexts are not loaded.

BTW,  is your Mojave upgrade to 10.14.5 beta?

0 Kudos
wickedcoyote
Contributor
Contributor
‎05-20-2019 07:38 AM

This was an upgrade from High Sierra to Mojave, currently running 10.14.4 

Security and privacy setting is set to app store and Identified Developers.

here is the kextstat output:

kextstat |grep vm 

188    1 0xffffff7f82cad000 0x11000    0x11000    com.vmware.kext.vmci (90.8.1) 2D72CD04-D6FF-3E84-B9B5-B4D5DCC8335F <13 6 5 3 1> 

189    0 0xffffff7f82cbe000 0x16000    0x16000    com.vmware.kext.vmnet (1299.21.09) 6522C084-7228-3B31-A465-1FB6697E4386 <188 6 5 3 1> 

190    0 0xffffff7f82cd4000 0x13000    0x13000    com.vmware.kext.vmx86 (1299.21.09) D9EB31E6-872E-3AD6-92AE-6BDEEA4D9055 <8 6 5 3 1> 

191    0 0xffffff7f82ce7000 0x7000     0x7000     com.vmware.kext.vmioplug.18.1.2 (18.1.2) DA0E15BD-577B-3C04-AD44-2A84AEA98E63 <56 6 5 3 1>

0 Kudos
jisv48
Contributor
Contributor
‎09-06-2019 05:50 PM

I have the same problem, but I upgraded from El Capitan to Sierra, with the caveat that I'm using an evaluation app for Fusion 11. I followed up some of the suggestions like removing and reinstalling but the problem persist. Some research indicated the need of having at the top directory a file named mach_kernel, but that is not being using by OSX any longer it appears now that that information is in the /System/Library/kernels. Can we create a symbolic link to this file?   Thanks

0 Kudos
ColoradoMarmot
Champion
Champion
‎09-08-2019 03:53 PM

Is Fusion 11 supported on Sierra?

0 Kudos