search

microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
10.11k stars 304 forks source link

VirtualBox no longer starts after updating to Windows11 and using WSL2 and WSLg #578

Open richtertoralf opened 2 years ago

richtertoralf commented 2 years ago 
Windows Version 21H2 (Build 22000.318)
Windows Subsystem for Linux WSLg Preview 1.026 (17.11.2021)
Oracle VirtualBox 6.1.28

After updating and using WSL2, VirtualBox no longer starts. Is this error known? I use few Linux distros under WSL2. But I have installed 20 different machines for network testing under VirtualBox. I can no longer start these virtual machines. I have already reinstalled VirtualBox as well. That did not bring any solution.

sabbyX commented 2 years ago

folks seem to hit similar/same issue ( MicrosoftDocs/WSL#798 ) on VirtualBox 6.1.28, downgrading to .26 might solve it. And well, VB and Windows Hypervisor doesnt go well together, you will end up using quirky workarounds at the end :)

rhyd42 commented 2 years ago

Virtualbox 6.1.30 has fixed a regression in 6.1.28 (Changelog) VMM: Fixed 6.1.28 regression preventing VMs starting when using Hyper-V mode on Windows 10

I'm able to boot Vagrant / Ubuntu images that I was using prior to enabling WSL2, they also work with Hyper-V enabled. They're about 10-12% slower than before, but perfectly usable for my needs.

crramirez commented 2 years ago

Enable Windows Hypervisor Platform component

richtertoralf commented 2 years ago

Thank you for the information. There are probably some dependencies between the different virtualization options that I don't completely understand. I have reset Microsoft Windows 11 Home and reinstalled it cleanly. Then I installed Oracle VirtualBox version 6.1.30. I can now start my virtual machines again. Since the focus of my work is a lab environment with many Linux virtual machines and networks, I will wait to test WSL2 and WSLG further.

Foosec commented 2 years ago

Virtualbox 6.1.30 has not fixed the regression for me. The newest working version as of right now is 6.1.26

pliniosampaio commented 2 years ago

Thank you for the information. There are probably some dependencies between the different virtualization options that I don't completely understand. I have reset Microsoft Windows 11 Home and reinstalled it cleanly. Then I installed Oracle VirtualBox version 6.1.30. I can now start my virtual machines again. Since the focus of my work is a lab environment with many Linux virtual machines and networks, I will wait to test WSL2 and WSLG further.

Tested here and it is working together. OS:

Virtual box

WSL:

CTBlaze commented 2 years ago

an old windows XP ova, that has been runing fine in 10+ years, also on my latest WIndows 11 Home with VB 6.1.32 (on AMD Ryzen 7 5800 U), does not work any longer after installing and activating WSL 2. Gets stuck at boot up. Oracle, what's wrong, why haven't you been able to steer clear of this in almost 2 years?

CTBlaze commented 2 years ago

re-confirmed on Windows 10 machine, 12 year old i7 mobile ,with WSL2 and VB 6.1.16 the same old XP OVA as mentioned above, that ran fine before install/update of WSL2, does get stuck on boot screen. I think the VB VMs do not get the resources they wish to claim, RAM allocation in task manager shows peanuts!

CTBlaze commented 2 years ago

Addtional info on my last two posts: VB 6.1.26 does not help at all, no difference. It must be the latest updates that have to do with WSL2. How can Oracle let it slip so much for so long (first reports I found were spring 2020). I would NEVER choose Oracle for any professional solution, with their product strategies, tbh... If this is a hidden war on virtualization technologies, they should all be ashamed to let the users suffer from it !!!