Highlighted
Enthusiast
Enthusiast

VMware Fusion 11.5.5 and 11.5.6 cause Mac OS 10.15.6 to crash when trying to run a Mac OS 10.14 guest

Jump to solution

I had this working for around a week but now every time I bring up the Mac OS 10.14 guest it crashes my whole MacBook Pro.

panic(cpu 3 caller 0xffffff800368b982): "attempting to register a sysctl at previously registered slot : 101"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.141.1/bsd/kern/kern_newsysctl.c:250

Backtrace (CPU 3), Frame : Return Address

0xffffff81f4123730 : 0xffffff800311a65d

0xffffff81f4123780 : 0xffffff8003254a75

0xffffff81f41237c0 : 0xffffff80032465fe

0xffffff81f4123810 : 0xffffff80030c0a40

0xffffff81f4123830 : 0xffffff8003119d27

0xffffff81f4123930 : 0xffffff800311a117

0xffffff81f4123980 : 0xffffff80038c1abc

0xffffff81f41239f0 : 0xffffff800368b982

0xffffff81f4123a20 : 0xffffff800336cf07

0xffffff81f4123a70 : 0xffffff80033a9a7d

0xffffff81f4123b00 : 0xffffff7f874f4419

0xffffff81f4123b70 : 0xffffff80037a0cac

0xffffff81f4123bc0 : 0xffffff800379dd03

0xffffff81f4123c30 : 0xffffff80037ac269

0xffffff81f4123c80 : 0xffffff80037abf99

0xffffff81f4123cf0 : 0xffffff80037bf7a2

0xffffff81f4123d60 : 0xffffff800317b9eb

0xffffff81f4123db0 : 0xffffff80031203c8

0xffffff81f4123e10 : 0xffffff80030f6d15

0xffffff81f4123e70 : 0xffffff800310db22

0xffffff81f4123f00 : 0xffffff800322c065

0xffffff81f4123fa0 : 0xffffff80030c1226

      Kernel Extensions in backtrace:

         com.vmware.kext.vmhgfs(1594.7.89)[A2FE5FBF-8BB7-32A7-B951-6DBED75D5A7F]@0xffffff7f874ed000->0xffffff7f874f8fff

BSD process name corresponding to current thread: kextd

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:

19G73

Kernel version:

Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64

Kernel UUID: 783946EA-6F11-3647-BF90-787AEA14B954

Kernel slide:     0x0000000002e00000

Kernel text base: 0xffffff8003000000

__HIB  text base: 0xffffff8002f00000

System model name: MacBookPro15,2 (Mac-827FB448E656EC26)

System shutdown begun: NO

System uptime in nanoseconds: 764263504773

last loaded kext at 764259777594: com.vmware.kext.vmhgfs 1594.07.89 (addr 0xffffff7f874ed000, size 49152)

last unloaded kext at 753823291958: com.vmware.kext.vmhgfs 1594.07.89 (addr 0xffffff7f874ed000, size 40960)

loaded kexts:

com.vmware.kext.vmhgfs 1594.07.89

com.vmware.kext.vmx86 1626.94.56

com.vmware.kext.vmnet 1626.94.56

@filesystems.smbfs 3.4.4

>!AGraphicsDevicePolicy 5.2.6

@fileutil 20.036.15

@AGDCPluginDisplayMetrics 5.2.6

>!AHV 1

|IOUserEthernet 1.0.1

|IO!BSerialManager 7.0.6f7

>!AUpstreamUserClient 3.6.8

>X86PlatformShim 1.0.0

>AGPM 111.4.4

>!APlatformEnabler 2.7.0d0

>pmtelemetry 1

>!A!IKBLGraphics 14.0.7

@Dont_Steal_Mac_OS_X 7.0.0

>AGDCBacklightControl 5.2.6

>ACPI_SMC_PlatformPlugin 1.0.0

>!AThunderboltIP 3.1.4

>BridgeAudioCommunication 6.70.7

>!ABacklight 180.3

>!AFIVRDriver 4.1.0

>!ABridgeAudio!C 6.70.7

>!AGFXHDA 100.1.429

>!AHIDALSService 1

>!A!IPCHPMC 2.0.1

>!ATopCaseHIDEventDriver 3430.1

>!A!ICFLGraphicsFramebuffer 14.0.7

>!AAVEBridge 6.1

>!A!ISlowAdaptiveClocking 4.0.0

>!AMCCSControl 1.14

@filesystems.autofs 3.0

@filesystems.apfs 1412.141.1

>BCMWLANFirmware4355.Hashstore 1

>BCMWLANFirmware4364.Hashstore 1

>BCMWLANFirmware4377.Hashstore 1

>!AFileSystemDriver 3.0.1

@filesystems.hfs.kext 522.100.5

@BootCache 40

@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1

@!AFSCompression.!AFSCompressionTypeZlib 1.0.0

>!AVirtIO 1.0

>!ABCMWLANBusInterfacePCIe 1

@private.KextAudit 1.0

>!ASmartBatteryManager 161.0.0

>!AACPIButtons 6.1

>!ASMBIOS 2.1

>!AACPIEC 6.1

>!AAPIC 1.7

$!AImage4 1

@nke.applicationfirewall 303

$TMSafetyNet 8

@!ASystemPolicy 2.0.0

|EndpointSecurity 1

>!A!BHIDKeyboard 209

>!AGraphicsControl 5.2.6

|IOAVB!F 850.1

>IOPlatformPluginLegacy 1.0.0

>!AHDA!C 283.15

|IOHDA!F 283.15

@!AGPUWrangler 5.2.6

>!ABacklightExpert 1.1.0

>!AHIDKeyboard 209

>X86PlatformPlugin 1.0.0

>!AThunderboltEDMSink 4.2.3

>!AThunderboltDPOutAdapter 6.2.6

>!AActuatorDriver 3440.1

|IONDRVSupport 576.1

>IOPlatformPlugin!F 6.0.0d8

>!AHS!BDriver 3430.1

>IO!BHIDDriver 7.0.6f7

>!AMultitouchDriver 3440.1

>!AInputDeviceSupport 3440.8

>!ASMBusPCI 1.0.14d1

|IO!BHost!CUARTTransport 7.0.6f7

|IO!BHost!CTransport 7.0.6f7

>!A!ILpssUARTv1 3.0.60

>!A!ILpssUARTCommon 3.0.60

>!AOnboardSerial 1.0

@!AGraphicsDeviceControl 5.2.6

|IOAccelerator!F2 438.7.3

|IOSlowAdaptiveClocking!F 1.0.0

>!ASMBus!C 1.0.18d1

|IOGraphics!F 576.1

@plugin.IOgPTPPlugin 840.3

|IOEthernetAVB!C 1.1.0

@kext.triggers 1.0

>usb.IOUSBHostHIDDevice 1.2

>usb.cdc.ecm 5.0.0

>usb.cdc.ncm 5.0.0

>usb.cdc 5.0.0

>usb.networking 5.0.0

>usb.!UHostCompositeDevice 1.2

>!AXsanScheme 3

>usb.!UVHCIBCE 1.2

>usb.!UVHCI 1.2

>usb.!UVHCICommonBCE 1.0

>usb.!UVHCICommon 1.0

>!AEffaceableNOR 1.0

|IOBufferCopy!C 1.1.0

|IOBufferCopyEngine!F 1

|IONVMe!F 2.1.0

>!AThunderboltPCIDownAdapter 2.5.4

>!AThunderboltDPInAdapter 6.2.6

>!AThunderboltDPAdapter!F 6.2.6

>!AHPM 3.4.4

>!A!ILpssI2C!C 3.0.60

>!A!ILpssDmac 3.0.60

>!AThunderboltNHI 5.8.6

|IOThunderbolt!F 7.6.1

|IOSurface 269.11

@filesystems.hfs.encodings.kext 1

|IOAudio!F 300.2

@vecLib.kext 1.2.0

>!ABCMWLANCore 1.0.0

>mDNSOffloadUserClient 1.0.1b8

>IOImageLoader 1.0.0

|IOSerial!F 11

|IO80211!FV2 1200.12.2b1

>corecapture 1.0.4

|IOSkywalk!F 1

>usb.!UHostPacketFilter 1.0

|IOUSB!F 900.4.2

>!A!ILpssI2C 3.0.60

>!A!ILpssGspi 3.0.60

>usb.!UXHCIPCI 1.2

>usb.!UXHCI 1.2

>!AEFINVRAM 2.1

>!AEFIRuntime 2.1

>!ASMCRTC 1.0

|IOSMBus!F 1.1

|IOHID!F 2.0.0

$quarantine 4

$sandbox 300.0

@kext.!AMatch 1.0.0d1

>!AKeyStore 2

>!UTDM 489.120.1

|IOSCSIBlockCommandsDevice 422.120.3

>!ACredentialManager 1.0

>!AFDEKeyStore 28.30

>!AEffaceable!S 1.0

>!AMobileFileIntegrity 1.0.5

@kext.CoreTrust 1

|CoreAnalytics!F 1

|IOTimeSync!F 840.3

|IONetworking!F 3.4

>DiskImages 493.0.0

|IO!B!F 7.0.6f7

|IO!BPacketLogger 7.0.6f7

>!ASSE 1.0

>KernelRelayHost 1

>!ASEPManager 1.0.1

>IOSlaveProcessor 1

|IOUSBMass!SDriver 157.140.1

|IOSCSIArchitectureModel!F 422.120.3

|IO!S!F 2.1

|IOUSBHost!F 1.2

>usb.!UCommon 1.0

>!UHostMergeProperties 1.2

>!ABusPower!C 1.0

|IOReport!F 47

>!AACPIPlatform 6.1

>!ASMC 3.1.9

>watchdog 1

|IOPCI!F 2.9

|IOACPI!F 1.4

@kec.pthread 1

@kec.corecrypto 1.0

@kec.Libm 1

1 Solution

Accepted Solutions
Highlighted
VMware Employee
VMware Employee

Your host's /var/log/install.log is likely to have a time-stamped record of the installation of VMware Tools onto your host.

The specific version of VMware Tools installed on your host was VMware Tools 11.0.6.  The installation images for VMware Tools 11.0.6 have so far been bundled with VMware Fusion 11.5.5 and/or 11.5.6.

Although VMware Tools installation images are bundled with VMware Fusion, the installation of Tools is a completely separate process.  Installing Fusion does not install Tools onto the host, and we would similarly expect that removing Fusion would not remove any existing installation of Tools from the host.

There is absolutely no facility in Fusion to install Tools onto the host, and I can not even think of any facility in Fusion which could malfunction in a way which would lead to Tools becoming installed onto the host, so it is a mystery how it got there.  One random thought: Are you perhaps using any odd software installation/distribution/migration/sync system which might have replicated the Tools installation from inside the VM onto your host?

(Just for the record: The bundled disk image which contains the installer for Tools for macOS is located at /Applications/VMware Fusion.app/Contents/Library/isoimages/darwin.iso, but Fusion only ever uses that disk image by attaching it to a macOS virtual machine for installation into that macOS virtual machine.)

Thanks,

--

Darius

View solution in original post

11 Replies
Highlighted
Enthusiast
Enthusiast

ARRGGGGGGHG!!!!!!

Now my MacBook Pro periodically crashes with:

Kernel Extensions in backtrace:

         com.vmware.kext.vmhgfs(1594.7.89)[A2FE5FBF-8BB7-32A7-B951-6DBED75D5A7F]@0xffffff

Even if I don't attempt to run Fusion.

I have followed this:

VMware Knowledge Base

But it still crashes!

0 Kudos
Highlighted
Enthusiast
Enthusiast

My MacBook Pro is unusable now.  It crashes every 10 minutes or so!

0 Kudos
Highlighted
Enthusiast
Enthusiast

This is a very similar issue to mine: Steve Q - So I upgraded to macOS Catalina...

I ran Remove VMWare Tools and my machine is not crashing.

0 Kudos
Highlighted
Enthusiast
Enthusiast

After reinstalling Fusion 11.5.5 my machine is stable again. 

It appears to be a bug in Fusion 11.5.6.

0 Kudos
Highlighted
VMware Employee
VMware Employee

Hi atj777 ,

Did you install tools to macOS 10.14 guest? Are you using a nested environment, say, install macOS VM, then install Fusion in the macOS VM.

0 Kudos
Highlighted
Enthusiast
Enthusiast

I did install VMWare Tools to the Mojave guest.

I do not have a nested environment.

Here is what I did:

  • Install Fusion 11.5.5 to my MacBook Pro running 10.15.6
  • Create a guest and install Mojave (10.14)
  • Install VMWare Tools to the guest (so I can share folders and have better screen resolution)
  • Install Lightroom 6.14 and Lotus Notes 10 to the guest
  • Used it successfully with no issues for a week
  • Left the guest running one night and awoke to a crashed computer (probably the suggested memory leak in 10.15.6)
  • Booted up and installed the suggested Fusion 10.5.6 upgrade (which I had previously put off) hoping it would fix the previous crash
  • Encountered the panic posted above every 10-20 minutes for a few hours
  • Removed Fusion from my MacBook Pro but still experienced the panic every 10-20 minutes
  • Found the Blog post linked above and removed VMWare Tools from the host - this stopped the panic every 10-20 minutes
  • Reinstalled Fusion 11.5.5 on the host
  • Rebuilt the trashed filesystem on the guest and reinstalled VMWare Tools, Lightroom and Notes

It has been working fine since and I no longer leave the guest running when I'm not using it.

0 Kudos
Highlighted
Community Manager
Community Manager

Apple's supplemental update should resolve the crashing overnight thing.

Regarding 'removinng vmware tools'... from the host?

They don't get installed on Hosts, they get installed in Guests.

I mean:

mike@OctoBook  /Library/Application Support/VMware > ll

total 8

drwxr-xr-x  5 root  wheel   160B Aug 11 20:04 VMware Fusion

drwxr-xr-x  2 root  wheel    64B Aug 11 15:10 VMware Horizon View

-rw-r-----  1 root  wheel   2.5K Aug 11 20:04 usbarb.rules

There should be no 'VMware Tools' folder on the host.

If it was there and you needed to remove it... Did you happen to install VMware Tools yourself on the host?

- Michael Roy - Product Line Manager: Fusion & Workstation
0 Kudos
Highlighted
Enthusiast
Enthusiast

The steps I listed above are what I did, so, no, I did not install VMware Tools to the host.

I know not to install it there and so I didn't.

It was only after searching for a solution for my constant panics, that I found the blog post linked above.  His solution was to run the Remove VMware Tools app, which I did.  I didn't put the app there.  All I did was search for it, find it, run it, and the panics went away.  Note that app was there even after I uninstalled Fusion.

From the comments on the Blog post, it appears multiple have had the exact same problem with the exact same solution.

Note that the app was not in the same location as mentioned in the Blog post.  I only found it by searching for "VMware" across the whole system.  I don't remember where it was, but it was somewhere odd.

0 Kudos
Highlighted
VMware Employee
VMware Employee

Your host's /var/log/install.log is likely to have a time-stamped record of the installation of VMware Tools onto your host.

The specific version of VMware Tools installed on your host was VMware Tools 11.0.6.  The installation images for VMware Tools 11.0.6 have so far been bundled with VMware Fusion 11.5.5 and/or 11.5.6.

Although VMware Tools installation images are bundled with VMware Fusion, the installation of Tools is a completely separate process.  Installing Fusion does not install Tools onto the host, and we would similarly expect that removing Fusion would not remove any existing installation of Tools from the host.

There is absolutely no facility in Fusion to install Tools onto the host, and I can not even think of any facility in Fusion which could malfunction in a way which would lead to Tools becoming installed onto the host, so it is a mystery how it got there.  One random thought: Are you perhaps using any odd software installation/distribution/migration/sync system which might have replicated the Tools installation from inside the VM onto your host?

(Just for the record: The bundled disk image which contains the installer for Tools for macOS is located at /Applications/VMware Fusion.app/Contents/Library/isoimages/darwin.iso, but Fusion only ever uses that disk image by attaching it to a macOS virtual machine for installation into that macOS virtual machine.)

Thanks,

--

Darius

View solution in original post

Highlighted
Enthusiast
Enthusiast
One random thought: Are you perhaps using any odd software installation/distribution/migration/sync system which might have replicated the Tools installation from inside the VM onto your host?

Ah!!!! That's it!

I had forgotten that in one last ditch attempt to get Lightroom 6.14 working on Catalina I used Time Machine to back up the VM and restore just the applications to the host.

It didn't cause me any problems at the time probably because I didn't reboot so the kernel extensions would not have been loaded.  When I had the crash due to the memory leak, the effective reboot would have enabled the kernel extensions and so the problems started.

OK. SO now I know what went wrong! Thank you!

Highlighted
VMware Employee
VMware Employee

Awesome!  That explains it all very nicely indeed.  With the macOS 10.15.6 memory leak issue plus the Time Machine backup transferring VMware Tools from the VM onto your host where it promptly crashed too, it surely has been a frustrating time for you.  Thanks for working with us to get it all explained, understood, and resolved.

--

Darius