I've been using VMware for the last 8 years on my mac with absolutely no issues. Today I started one of my VM (Debian 😎 and after the guest started and ran for 5mn I got a "VMWare Fusion has encountered an error and has shut down the virtual machine." error without much more details.
I was running on VMware Fusion 10.1.16 and Mojave 10.14.6. I then tried other Linux VMs and they all had the same issue after few minutes of operation. I tried Windows VMs with similar results.
I decided to purchase an upgrade to VMware Fusion 11.5.1 and I got exactly the same problem.
I've tried to disable/enable "Accelerate 3D Graphics", Intel VT-x/EPT. I've tried several Hardware Versions (from 6 to 16), without any success.
I do not know what changed on my computer since last time VMware was running flawlessly; maybe an update from 10.14.5 to 10.14.6?
I have generated some VMware Fusion Problem Reports but I don't know where to look to see what is causing this error/shut down?
OK got it fixed thanks to Technical Support (Santhosh Kumar).
In the logs there was:
2019-12-06T09:43:12.141+01:00| mks| I125: Beginning monitor coredump
2019-12-06T09:43:12.241+01:00| mks| I125: CoreDump error: Read, page 0xc33 (0x20b127) Bad address
2019-12-06T09:43:12.247+01:00| mks| I125: CoreDump error: Read, page 0xd13 (0) Bad address
2019-12-06T09:43:12.247+01:00| mks| I125: CoreDump error: Read, page 0xd14 (0) Bad address
2019-12-06T09:43:12.247+01:00| mks| I125: CoreDump error: Read, page 0xd15 (0) Bad address
2019-12-06T09:43:12.247+01:00| mks| I125: CoreDump error: Read, page 0xd16 (0) Bad address
2019-12-06T09:43:12.467+01:00| mks| I125: End monitor coredump
2019-12-06T09:43:12.807+01:00| mks| I125: Msg_Post: Error
2019-12-06T09:43:12.807+01:00| mks| I125: [msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (mks)
2019-12-06T09:43:12.807+01:00| mks| I125+ MKS MacOSKeyboard: Keyboard thread failed to respond to ungrab request
So the crash appears to be coming out of a keyboard code: VMware Knowledge Base
I added the following config option to my vmx (Hold the Option (Alt) key and right-click the virtual machine) file :
mks.keyboard.setHostLEDs=FALSE
And it's now working back like in the 40s!