Could this be a bug in VMware Fusion / VMware Tools when nested virtualization is enabled?
To recreate the problem:
This is a very simple test without anything special: fresh install with no additional 3rd party SW on Guest OS.
If Virtual Machine Platform is not enabled I don't see this BSOD.
Other kinds of BSOD also happen occasionally. List of BSOD stop codes observed so far with this setup:
Also if WSL and Virtual Machine Platform are disabled, but Hyper-V is enabled: BSOD happens. Only when nested virtualisation is completely disabled is when I experience a stable Guest OS environment.
Anyone can recreate and confirm this? If so, could a VMware engineer look into this?
Here's an update: After uninstalling VMware Fusion Tools, rebooting, BSOD is still happening. 😣
Also, I've migrated this Guest OS to Parallels Desktop on Big Sur, enabled nested virtualisation: No problem. I installed ubuntu on WSL2 and so far no issue.
My assessment so far: The problem seems to lie with VMware Fusion (and perhaps how it integrates with Apple's Hypervisor Framework?) and not VMware Tools.
I want to say I've been experiencing the exact same issue -- also just within the last couple of days. In my Win10Pro guest OS, I didn't have Virtual Machine Platform or WSL turned on, but I did have the Hyper-V and Containers features enabled. Was getting the same "CRITICAL PROCESS DIED" BSOD at seemingly random intervals after reboot. I turned off the Hyper-V feature only, and have been running fine for a few hours since then.
Around the same time as the BSODs started happening, the main software I use on Windows (SQL Server Management Studio) started crashing randomly. I did have some updates for it that were installed around the same time, though, so it's hard to say if the issue is related to the BSOD or not. Both issues started showing up after installing the latest VMware Tools Guest Additions package (11.2.6, build-17901274).
Good to know this was happening for you on a fresh install -- saves me the trouble!
A couple more notes: I'm also on Big Sur on Intel, but only macOS 11.2.3. I am on Fusion Player 12.1.2. I would guess that the latest fusion point release is the culprit. If you can get ahold of a 12.1.1 installer, it might be worth a try...