Hi,
The opening post has this snippet in the supplied log:
2021-10-27T13:16:51.956Z In(05) mks Metal Device plugin: AppleIntelHD4000GraphicsMTLDriver 16.4.5 10
2021-10-27T13:16:51.956Z In(05) mks Metal Device: Pull Model Interpolation support: No
2021-10-27T13:16:51.956Z In(05) mks MTLRenderer: Enabling workaround for depth zeroing
2021-10-27T13:16:51Z[+0.000] Wa(03) mks Caught signal 6 -- tid 13466 (addr 7FF80DF0F112)
2021-10-27T13:16:51Z[+0.000] In(05) mks SIGNAL: rip 0x7ff80df0f112 rsp 0x70000dc48718 rbp 0x70000dc48740
Which indeed makes it look like the crash is GPU related (check your log if you have this issue as the error itself can mean other things too)
For a GPU related issue like this, chances are you can workaround it by disabling 3D acceleration in your VM configuration.
With the VM shut down go to menu: Virtual Machine -> settings -> Display
and uncheck the Accelerate 3D graphics option down there.
You might be able to tweak the settings there too in some configurations.
Hope this helps,
--
Wil
Hi,
@MitchInSeattle wrote:
Also having the same issue on a 16" 2021 Macbook Pro running Monterey 12.0.1 and Fusion 12.2.1 when importing an existing VM or trying to create a new one.
That's an M1 machine isn't it?
If so then you can't run Fusion 12.2.1 on it as you'll need to run the Apple Silicon Tech Preview instead.
This can be found here: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon-Tech/bd-p/160004
Note however that you can't bring ANY old intel based VM's to your fancy new M1 machine.
No intel virtual machines will run now (or in the future) on your new apple hardware.
That would require emulation of the processor and that's not something that VMware (or any of its competitors) offer. Rosetta also does not help you here as it is too low level for it to take care of that.
You will have to create new Arm based VM's on the M1 machine and the only type of OS that is currently supported on the Tech Preview is Linux.
--
Wil
@ColoradoMarmot wrote:
You'll get a similar error if you try to run 12.x on an M1 chip. You have to use the tech preview for that.
Same error even.
That's the problem with this particular error, it's utterly vague and can mean a lot of things.
What it is basically trying to say is "your VM crashed while trying to start, something went wrong and we can't connect to it"
What the "something" is might be different for everyone in this thread.. which makes it hard to help troubleshooting. Most useful are the mksSandbox.log and the vmware.log, both of which can be found in the VM's bundle.
If those 2 files then gives other users like us a proper hint.. isn't certain, but without that it will be guess work for sure.
It should hopefully give a vmware employee enough to pinpoint what is happening.
--
Wil