Fusion 11.5.6 on macOS 10.15.6 (19G2021): Encountered an error and has shut down the virtual machine

[Splaktar]

I can't seem to use VMWare Fusion anymore after the 11.5.6 update due to the above error, which includes no helpful information at all.

Here's some of my log output:

Sep 17 02:04:34 splaktar com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.activateSettings.29986😞 Failed to bootstrap path: path = /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/Resources/activateSettings, error = 2: No such file or directory

Sep 17 04:05:34 splaktar com.apple.xpc.launchd[1] (com.apple.bsd.dirhelper[30016]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.bsd.dirhelper

Sep 17 00:03:39 splaktar xpcproxy[29957]: libcoreservices: _dirhelper_userdir: 557: bootstrap_look_up returned (ipc/send) invalid destination port

Sep 17 06:06:57 splaktar transparencyd[1286]: libcoreservices: __makeDirectory: 405: mkdir: path=/var/folders/mz/pjttw4vs5xs33pzstmq1h7140000gn/T/com.apple.transparencyd//TemporaryItems/ mode=0700: Operation not permitted

Sep 17 09:03:52 splaktar idea[32092]: allVms required 1.8*,1.8+

Sep 17 09:03:52 splaktar idea[32092]: Current Directory: /Users/splaktar/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/202.7319.50/IntelliJ IDEA.app/Contents/MacOS

Sep 17 09:03:52 splaktar idea[32092]: Value of IDEA_VM_OPTIONS is /var/folders/mz/pjttw4vs5xs33pzstmq1h7140000gn/T/toolbox-temp16485711294035985963/202.7319.50.vmoptions

Sep 17 09:03:52 splaktar idea[32092]: Processing VMOptions file at /var/folders/mz/pjttw4vs5xs33pzstmq1h7140000gn/T/toolbox-temp16485711294035985963/202.7319.50.vmoptions

Sep 17 09:03:52 splaktar idea[32092]: Done

Sep 17 09:38:27 splaktar Google Chrome[461]: BUG in libdispatch client: mach_recv, monitored resource vanished before the source cancel handler was invoked { 0x7fa4ee40c670[source], ident: 78339 / 0x13203, handler: 0x109f9d220 }

Sep 17 09:38:28 splaktar com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100006.Aqua😞 Caller not allowed to perform action: loginwindow.232, action = service removal, code = 150: Operation not permitted while System Integrity Protection is engaged, uid = 0, euid = 501, gid = 20, egid = 20, asid = 100006

Sep 17 22:57:33 splaktar com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.vmware-vmx.14805😞 Failed to bootstrap path: path = /Applications/VMware Fusion.app/Contents/Library/vmware-vmx, error = 2: No such file or directory

Sep 17 22:57:33 splaktar syslogd[142]: ASL Sender Statistics

Sep 17 22:57:41 splaktar com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0600-0000-0000-000000000000[14793]): Service exited due to SIGKILL | sent by mds[7206]

Sep 17 22:57:49 splaktar com.apple.xpc.launchd[1] (com.vmware.IDHelper[14812]): Service exited with abnormal code: 255
Sep 17 22:57:49 splaktar com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.diskutil.14910😞 Failed to bootstrap path: path = /usr/sbin/diskutil, error = 2: No such file or directory

I verified that /Applications/VMware Fusion.app/Contents/Library/vmware-vmx, /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/Resources/activateSettings, and /usr/sbin/diskutil do exist.

I'm not getting any prompts in "Settings & Privacy" and "VMWare Fusion.app" has Full Disk Access.

I removed the VM from my VM Library and added it back, but that didn't help. I restarted the VMWare Fusion app, but that didn't help.

[Splaktar]

My vmware-0.log has this as well:

2020-09-18T09:35:09.021-05:00| vcpu-0| I005: Guest: About to do EFI boot: cloudready

2020-09-18T09:35:12.770-05:00| vcpu-0| W003: MONITOR PANIC: vcpu-0:IOAPIC: regSelect=0x8

2020-09-18T09:35:12.770-05:00| vcpu-0| I005: Core dump with build build-16696540
2020-09-18T09:35:12.772-05:00| vcpu-0| I005: Writing monitor `vmmcores.gz`

2020-09-18T09:35:12.785-05:00| vcpu-0| W003: Dumping core for vcpu-0
2020-09-18T09:35:12.785-05:00| vcpu-0| I005: Beginning monitor coredump

2020-09-18T09:35:12.865-05:00| vcpu-0| I005: CoreDump error: Read, page 0xd1a (0) Bad address

2020-09-18T09:35:12.865-05:00| vcpu-0| I005: CoreDump error: Read, page 0xd1b (0) Bad address

2020-09-18T09:35:12.865-05:00| vcpu-0| I005: CoreDump error: Read, page 0xd1c (0) Bad address

2020-09-18T09:35:12.865-05:00| vcpu-0| I005: CoreDump error: Read, page 0xd1d (0) Bad address

2020-09-18T09:35:12.936-05:00| mks| W003: Panic in progress... ungrabbing

2020-09-18T09:35:14.074-05:00| vcpu-0| W003+ The core dump limit is set to ZERO; no core dump should be expected

2020-09-18T09:35:14.074-05:00| vcpu-0| I005: Msg_Post: Error
2020-09-18T09:35:14.074-05:00| vcpu-0| I005: [msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (vcpu-0)

2020-09-18T09:35:14.074-05:00| vcpu-0| I005+ vcpu-0:IOAPIC: regSelect=0x8

2020-09-18T09:35:14.074-05:00| vcpu-0| I005: [msg.panic.haveLog] A log file is available in "/Users/splaktar/Virtual Machines.localized/CloudReady Home v66.4 x64.vmwarevm/vmware.log". 

2020-09-18T09:35:14.074-05:00| vcpu-0| I005: [msg.panic.requestSupport.withoutLog] You can request support. 

2020-09-18T09:35:14.074-05:00| vcpu-0| I005: [msg.panic.requestSupport.vmSupport.apple.menu]

2020-09-18T09:35:14.074-05:00| vcpu-0| I005+ To collect data to submit to VMware support, choose "Collect Support Information" from the "Help" menu.

2020-09-18T09:35:14.074-05:00| vcpu-0| I005+ You can also run "VMware Fusion Problem Reporter.tool" inside the VMware Fusion application bundle directly.

2020-09-18T09:35:14.074-05:00| vcpu-0| I005: [msg.panic.response] We will respond on the basis of your support entitlement.

2020-09-18T09:35:14.074-05:00| vcpu-0| I005: ----------------------------------------

[Splaktar]

Based on VMware Fusion 11.5.6 Release Notes:​

VMware Fusion causes macOS 10.15.6 hosts to operate unreliably

VMware Fusion might cause a macOS 10.15.6 host to hang, panic, or unexpectedly restart after a virtual machine has been running for a period of several hours or more. Users are forcibly logged out and lose their current session and data.

Restart your Mac regularly to avoid failure. If macOS 10.15.6 has not yet been deployed on a host, consider deferring deployment until the issue has been resolved.

It seems like macOS is what's broken and now I'm stuck until a patch is released for this in Fusion 11.5.7.

I downloaded and installed 11.5.5 and I still have the same problem. I updated that to 11.5.6 and still saw the same problem.

So it seems like VMWare Fusion is just not supported at all on the latest version of macOS Catalina

[Mikero]

The issue you cite and the issue you're experiencing I think are two separate things.

The issue cited is experienced only "after a virtual machine has been running for a period of several hours or more"  and was resolved in macOS 10.15.6 supplemental update: https://support.apple.com/kb/DL2049?locale=en_US

     "- Fixes a stability issue that could occur when running virtualization apps"

The crux of your issue, without any other context, is:

MONITOR PANIC: vcpu-0:IOAPIC: regSelect=0x8

Why it's getting there is the question.

Can you share info about your hardware?

Mac Model?

What you're doing when this error happens?

a full vmware.log from when it crashes would also be helpful.

[Splaktar]

Ah OK, thank you for the clarification.

MacBook Pro 2018 15" with i9 and Vega 20 with 16 GB RAM.

I restarted the VM to apply an update and I haven't been able to start it again. The same error always occurs.

OK, I'll post a full log soon.

[Splaktar]

vmware.log attached.

Thank you for taking a look.

[wila]

Hi,

Not sure what happened, but to me it seems that your update to 11.5.6 did not get installed completely

The log file has this as the top line (emphasis mine):

2020-09-18T10:17:07.382-05:00| vmx| I005: Log for VMware Fusion pid=18693 version=11.5.5 build=build-16269456 option=Release

My suggestion would be to drag your VMware Fusion to the bin (uninstall), then download the full installer from:

https://my.vmware.com/web/vmware/downloads/details?downloadGroup=FUS-1156&productId=798&rPId=39198

reboot the mac, install VMware Fusion that you just downloaded.

Does the problem still occur?

If so, please attach a new vmware.log

--

Wil

[Splaktar]

Ah yeah, I think that must have been after reinstalling and trying with 11.5.5. I grabbed vmware-0.log instead of vmware.log.

Here's one from 11.5.6.

Sorry about that. Yes the problem is still occurring and I am unable to use Fusion.

[Splaktar]

Hello,

I attached the updated log file some time ago. Can anyone take a look at it?

Thank you

[ColoradoMarmot]

Did you just do the update, or did you get the combo update and apply that?  If you did the former, try the latter - it does a complete rollup from .0.

Backup before hand of course 🙂

[Splaktar]

The Fusion update? Yes, I updated from 11.5.5 to 11.5.6. Then I uninstalled and tried with 11.5.5 again, saw the same issues, and updated to 11.5.6 again.

Can you please point me to the "combo update"?

[ColoradoMarmot]

No, the combo update to 10.15.6.  Sometimes that cleans things up and resolves strange issues.

[wila]

Hi,

Sorry about that, it slipped through (I did look at your log earlier, but didn't see anything standing out)

A couple of remarks. I see that you have a lot of devices attached to your mac, it might be that one of them is triggering something unexpected.

One of the things that stood out to me is that it sees a lot of keyboard devices.. weird.

You might want to try the .vmx edit from Darius here:

Re: Problem when host (Mac) is going to sleep

--

Wil

[Splaktar]

I gave that a shot, unfortunately it didn't help. I restarted the VM a few times but it kept crashing the same as before.

I'll try creating a whole new VM image from scratch to see if that will work.

[Splaktar · Accepted solution]

OK, in this case my original VM isn't super valuable. So I was able to re-download the latest .ova file and import it to create a new VM. With the new image, everything seems to be working fine. I'm not sure why the old image failed during upgrade, but I'll move on.

Thank you for the helpful responses and taking a look at my log files!