Comment 8 for bug 1890006

I've spent a day trying to figure out why my VMs were not working until I found this report.

TLDR: Windows Sandbox in itself does not break the virtualization for Virtualbox, what does is the Virtual Machine Platform (on which I guess Windows Sandbox depends on).

I'll try to gather everything I experienced so someone smarter can make use of it:

So I upgraded to WSL2 which requires Virtual Machine Platform to be enabled. Couple of days later I tried opening an existing, already configured and previously working VM with Ubuntu Server 20.04, it got stuck at trying to perform some RAID6 xor check (excuse my incompetence). Shut down the VM, restore to a stable snapshot, now it got stuck at "Loading essential drivers...". Shut down, restore snapshot, reset voltages in Throttlestop (undervolt), reboot. Now the VM starts for some reason, super slow though, and I'm getting Hash Sum mismatch on apt update/upgrade. Tried a desktop Ubuntu VM, starts super slow, same mismatch error. WSL and my Linux server works fine on the same network, so that's not the issue. Finally I found this thread, and indeed, Virtualbox was running in native API execution engine, disabled Virtual Machine Platform in Windows, reboot, voila, works!

I guess don't upgrade to WSL2 if you intend to use Virtualbox (WSL1 does not need Virtual Machine Platform).