[jsheard]

AIUI they already had to do something similar on Windows. Enabling certain features causes Windows to boot itself inside Hyper-V, and VMwares own hypervisor can't run nested under the Hyper-V hypervisor, so VMware gives up and runs its guests directly on Hyper-V instead.

[patmorgan23]

Windows basically always runs inside a hyper-v VM these days.

[naikrovek]

Only if Hyper-V is enabled and/or WSL2 is installed. And Hyper-V is a prerequisite for WSL2.

If hyper-V is not enabled, then you’re running on metal.

You may notice a longer than normal reboot time when enabling or disabling Hyper-V compared to a normal reboot, and this is why; you’re moving from running on silicon to running in a privileged management VM or vice versa.

[terinjokes]

Virtualization (Hyper-V) can also be enabled, without enabling the Hyper-V Manager or WSL2 Windows Components, if the "Core Isolation" security setting is enabled.

[NikkiA]

The biggest telltale for me is that hyper-v and wsl breaks anything that uses the ethernet mac as part of a host-id, and mobaxterm is unable to run it's X11 server because something about the hyper-v virtual ethernet screws it

[pjmlp]

Or enabled the security features anyone should be running in first place, thus yeah since Windows 11, it is for all practical purposes.

Same applies to XBox Windows flavour.

[intelVISA]

IOMMU is my borrow checker