Opened 4 years ago
Closed 2 years ago
#19987 closed defect (obsolete)
VirtualBox 6.1.16 and Hyper-V Compatibility issue (prevents using WSL2)
| Reported by: | chli | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.16 |
| Keywords: | hyperv, wsl2 | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
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!
Attachments (3)
Change History (8)
by , 4 years ago
| Attachment: | kernel-boot-hyperv-off.txt added |
|---|
by , 4 years ago
| Attachment: | kernel-hang-hyperv-on.txt added |
|---|
by , 4 years ago
| Attachment: | Debian-sid-dev-2020-10-21-14-21-41.log added |
|---|
comment:1 by , 4 years ago
comment:3 by , 4 years ago
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.
comment:4 by , 4 years ago
Could you please attach the VBox.log files of the affected VMs? The one attached is the hardened log not tha actual VM log.
comment:5 by , 2 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Other good reports of issues are here: https://forums.virtualbox.org/search.php?keywords=wsl2&t=90853&sf=msgonly