Allow host to run other hypervisor (via Nested virtualization)
Currently Hyper-V locks out other virtualization apps when installed on host. But it is also said that Hyper-V upon installation essentially makes a "host" just another (although privileged) guest. Likewise, we know that nested VMs are supported for a while now. And I tested, it does support other 3rd party virtualization software in a guest.
So why not allow (even if only via Powershell) option to enable "nested" for a host OS as well?
Current workaround is : Windows host with Hyper-V -> Windows guest VM for which nesting was enabled -> 3rd party hypervisor -> <something running in it>
As use case, I can point to Android emulators. Android is badly supported by Hyper-V, mostly because of ARM/x86, and lousy support of Android-x86. BUT multiple (good) emulators exist, like BlueStacks... yet they all (to my knowledge) require VTx exposed.
I'm attaching MS's own nesting example. Please see how "Windows Root OS" is placed on top of Hypervisor, it just needs the nesting exposed as well.
Karl Wester-Ebbinghaus (@tweet_alqamar) commented
There are different roles one is Hyper-V and the other one allows to run Virtual Box and sorts on a Hyper-V machine. I am not sure what you are asking for.
This issue is forcing me to drop Windows on my machines. We need nested virtualization!
Rob Kearey commented
Given that so much development upskilling relies on virtualbox via vagrant, this is an absolute requirement for windows to be taken seriously as a cloud development platform.
Markus Krainz commented
I am the creator of a similar bug report on github with more information: https://github.com/microsoft/WSL/issues/5030
Yes, please, I want this! No, Virtualbox/Vmware workstation backends for Hyper-V are not enough. We need nested VT-x/AMD-V in the root domain.