[rzzzt]

If I got it right, once Hyper-V is enabled, your existing Windows installation boots on top of/under/alongside the hypervisor (kinda-sorta like Xen's Dom0). This setup prevents other virtualization solutions from running, but allows the use of Windows Sandbox, WSL2 as well as regular Hyper-V VMs.

[ch_123]

It is now possible to run other hypervisors with Hyper-V enabled, but there is usually a performance penalty. See:

https://blogs.vmware.com/workstation/2020/05/vmware-workstat...

https://docs.oracle.com/en/virtualization/virtualbox/6.0/rel...

[nickflood]

This feature, at least in VirualBox, is useless. Machines that run hyper-v core do not boot properly, have their memory corrupted at boot, etc.

I wanted to use various things that rely on Hyper-V such as the Sandbox and WSL2 (last tried it in June), but the brokenness of VirtualBox forced me to abandon those technologies.

[rzzzt]

I still haven't decided which one is better, "buying in" fully on Hyper-V or sticking with a set of separate solutions, eg. MSYS2 instead of WSL2, Docker Toolbox vs. Docker for Windows, Linux VMs in VirtualBox on an as-needed basis, etc.