Stop blaming Hyper-V for "crippling other VM software". You ever tried to run VBox and KVM together? It's a limitation of the processor's virtualization extension.
The complaint is not necessarily with Hyper-V itself, it is with WSL2 requiring Hyper-V, thus stopping you from using WSL2 and VBox (or VMware) on the same machine - though apparently they have very recently fixed this.
Problem is once Hyper-V is installed and enabled, no other VM can even be started regardless of no Hyper-V VMs actually running. This limitation does not exist on linux afaik. I have run libvirt based VMs and VirtualBox VMs at the same time on linux just fine in the past.
That’s not what’s happening. Hyper-v is a type-1 hypervisor. When it’s running, even your Windows instance is running within hyper-v. Windows 10 has the hypervisor platform that lets other vm developers hook into the hyper-v host architecture, that’s how you can get android emulators and virtualbox running under hyper-v. It all works fine but is a little unintuitive to set up.
Most likely you just wasn't using VirtualBox own virtualization since it's cant work alongside with KVM. Current version of virtualbox just use KVM just like libvirt.
Although, I don’t know if both kinds of VMs can run in parallel. I recall at least doing so with VMWare in the past.
The thing is, when enabling Hyper-V on Windows, you can’t do anything without fully rebooting. On Linux I know for a fact you do not need to reboot to switch between VMs.
Hyper-V is a type 1 hypervisor. Even windows runs within it when enabled. Comparing to KVM would be better rather than VBox or VMWare. Try VBox with KVM to see same effect.
