Virtualbox 6.1 and WSL2 with Windows 10 2004

[owl]

Hi, I have recently updated to Windows 10 2004 and all these components work fine together:

- WSL2 with Ubuntu
- Docker Desktop
- VMWare Workstation 10: with new installs of MX Linux, Linux Mint and Windows 10

However I cannot get a single OS installed under Virtualbox. When I try, something usually goes wrong, e.g.:

- MX Linux: cant get past the 'start init' boot sequence
- Linux Mint: Frozen on boot
- Windows 10: Corrupt files during install

Note, I do not have "Hyper-V" ticked in 'Windows Features'. However I do have "Windows Subsystem for Linux" ticked.

Is there some setting I need to configure in Virtualbox, or does Virtualbox still have issues with Hyper-V? Thanks.

[BillG]

Yes. WSL2 prevents VirtualBox accessing hardware virtualization, just like Hyper-V, Credential Guard, Device Guard and so on.

[ycollet]

On my Windows 10 2004, WSL is deactivated and I still have periodic hangs of VirtualBox (several times a day).
That was not the case before installing 2004 update.

[owl]

I thought virtualbox and hyper-V/wsl2 now work together:

https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq

To quote...

Some 3rd party applications cannot work when Hyper-V is in use, which means they will not be able to run when WSL 2 is enabled, such as VMware and VirtualBox. However, recently both VirtualBox and VMware have released versions that support Hyper-V and WSL2!

So what am I not understanding?

[mpack]

So what am I not understanding?

Yes, VirtualBox has introduced support for running under Hyper-v. Kinda. It doesn't work well as yet, apparantly because Microsoft keep changing it.

[owl]

Ok thanks for clearing that up.

[tmanev]

Someone having an idea when VirtualBox will provide a fix for it.

[scottgus1]

No idea when, but the devs are working on it. The Oracle customers want Virtualbox running under Hyper-V, but Microsoft makes its OS's a moving target now, so the devs have to catch up. It is getting better. See the saga here: VirtualBox 6.0 and Hyper-V

[hnyman]

Someone having an idea when VirtualBox will provide a fix for it.

The 6.1.15 test builds work pretty ok. Some of the bugs have been ironed out.

(I have used 6.1.15-140351 and 6.1.15-140592, and I am just installing the new 6.1.15-140728)

Ps. There is not only Microsoft to blame, but also some pretty old Virtualbox bugs have been found recently.
Fox example,
bug fixed by https://www.virtualbox.org/changeset/86067/vbox
originates in https://www.virtualbox.org/changeset/72403/vbox in May 2018