Just record some more details for the errors I met. Maybe it's not a bug of `WSL doc` nor WSL2, but Windows (Hyper-V API) or VirtualBox. If you enable even Sandbox (which uses only one Hyper-V service), for example, Virtualbox doesn't run. Hyper-V Powering Windows Features (2019.12.12) The 6.1.0_BETA1 seemingly fixed it (but in fact it just accidentally disabled the optimization, so it was REALLY slow), and 6.1.0_RC1 restored the optimization which means that it doesn't work again with 19. Hyper-V usage by VirtualBox started working with 1809, and some change in 1903 broke it. To use Virtualbox properly, for now*, you have to have Hyper-V off, which turns off anything that uses Hyper-V. Yes, WSL2 is not compatible with Virtualbox, due to WSL2 using Hyper-V, which uses VT-x exclusively and doesn't share it with Virtualbox. Yes, Hyper-V and VirtualBox 6.0 looks can play together, as the Oracle document you mentioned as well as the here (those time there is no WSL2 yet).īut now it really looks problem to have WSL2 together with VirtualBox,Īre WSL 2 and VirtualBox currently mutually exclusive?
0 Comments
Leave a Reply. |