VirtualBox 6.1.16 and Hyper-V Compatibility issue (prevents using WSL2)

[chli]

Hi,

I had hope that VirtualBox 6.1.16 would resolve the pending issues with Hyper-V so I can enjoy both VirtualBox and WSL2 but that's not yet the case (it seems to be the case for some though).

After running as administrator:

bcdedit /set hypervisorlaunchtype off

And rebooting, I can start my Debian VM without issues. But if I set :

bcdedit /set hypervisorlaunchtype auto

And rebooting, then my Debian VM doesn't boot, the Kernel hangs during initialization.

Attached are VirtualBox logs and Linux Kernel logs (with HyperV ON and OFF) (5.9-amd64)

Thank you!

[Aren Cambre]

Other good reports of issues are here: ​https://forums.virtualbox.org/search.php?keywords=wsl2&t=90853&sf=msgonly

[Aren Cambre]

#20033 and #19766 seem to duplicate this.

[Cito]

See also ​https://github.com/MicrosoftDocs/WSL/issues/798 and ​https://github.com/MicrosoftDocs/WSL/issues/536 (which shouldn't have been closed because it is still not fixed).

It got a lot better in 6.1.6 but there are still crashes depending on the host hardware and guest OS. It's sad that it's still not possible to use VB and WSL 2 together.

[aeichner]

Could you please attach the VBox.log files of the affected VMs? The one attached is the hardened log not tha actual VM log.