WSL: WSL 2 needs Hyper-V enabled. But this conflicts with 3rd party software ( No nested VT-x in the root domain )
WSL 2 needs Hyper-V enabled. But this conflicts with 3rd party software like VMware or Virtualbox.
It is the same issue as why those tools will not run with Windows Defender Credential Guard enabled.
The official solution as per the FAQ is that VMware and Virtualbox change their software so it uses the Hyper-V backend instead of their own via the Hypervisor Platform API. [2] However this API has been buggy for the last few Windows builds and after 2 years it is still not stable. [4]
Wouldn’t it be easier to just enable ExposeVirtualizationExtensions globally? Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
So that if Vmware or Virtualbox are started they will be able to access the Intel VT-x (and AMD equivalent) instructions?
Basically I finally want to be able to run WSL2 while still keeping the Virtualbox support that I rely on. And I don’t want to wait another 2-3 years until the Hypervisor Platform API matures and then probably still having performance regressions.
Can I enable ExposeVirtualizationExtensions for the client that the main Windows 10 OS runs in. Not talking about inside WSL2 client here. I don’t know what to put for the VMName though. Is this feasible?
[1] https://superuser.com/questions/1208850/why-cant-virtualbox-or-vmware-run-with-hyper-v-enabled-on-windows-10/1291879#comment2284544_1291879 [2] https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq [3] https://docs.microsoft.com/en-us/virtualization/api/ [4] https://forums.virtualbox.org/viewtopic.php?t=90853
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 57
- Comments: 33
@therealkenc genius. Closing the issue without any comment or reply. Please forward the issue to the proper people if you are not the right person to tackle this. Thanks!
Still not working. Bummer!!
It really sucks need to manually ‘switch’ this hyper off/auto if I want to get VBOX(W10) working or WSL2…
hypervisorlaunchtype auto --> enables WSL2 & disables w10 VBOX hypervisorlaunchtype off --> disables WSL2 & enable w10 VBOX
So is this resolved?
April 24th, 2022 and we still need to toggle
hypervisorlaunchtypeand reboot in order to switch between using WSL2 or VirtualBox.Bump
I just updated to 20251.1 and WSL2 and VMware Workstation 16 works together. hypervisorlaunchtype is set to Auto. The issue is finally fixed for me.
can’t believe this is still broken. wsl2 is dead to me until this is fixed 😦
You can also simply use Windows Features and enable/disable WIndows Virtual Machine. Both options; bcdedit and Win Features require a reboot,
Ridiculous in the post-2020 Cloud era we have to deal with these incompatibilties and lack of vendor support on these issues.
No wonder Virtualbox has always been unstable with Hyper-V backend. Since May 2018 the implementation was broken and CPU registers under HyperV had wrong values. That means instability, crashes, data corruption in downloads and disk, and so on.
This fix in latest test builds (>=r140351) should make Virtualbox finally usable with the Hyper-V backend.
Wow so shameful.
this is so ridiculous <insert facepalm>
Still nested virtualization on VMWare not working within “bcdedit /set hypervisorlaunchtype auto” mode, So we can not have Docker Desktop ( Hyper-V or WSL/2) in Windows & VMWare with nested virtualization on windows at the same time! Shhhhhhhh
As of VMware’s Workstation version 15.5.5, Windows Hyper-V and VMware Workstation (again, 15.5 and greater) can coexist.
Here’s VMware’s take on that: https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html
This is precisely my problem. I want wsl2 alongside 3rd Party Virtualization solutions WITH 3D graphics acceleration enabled in order to keep playing old games. Until this problem is resolved, I am not going to update from wsl to wsl2.
Virtualbox 6.1 works with WSL 2
This is not nested virtualization, but the use of hyper-v interface. This is more like vmware panel controlling hyper-v, and is precisely what is not wanted.
Sorry, it’s not in microsoft’s interest to allow this, so they’ve intentionally done this to make that not possible.
VMWare Player 16 works for me with WSL 2, but nested virtualization is not supported and graphics acceleration too 😦
VMWare version - 16.0.0 build-16894299 Windows 10 version - 19041
Virtualize Intel VT-x cannot be set -> graphics acceleration cannot be enabled I use VMWare player only for old games and with WSL 2 VMWare is useless for this.
They can coexist but 3D acceleration is NOT working, because nested virtualization is not working 😦
Thanks for the reply @therealkenc. #4193 is already linked above, but a different problem.
I am happy that MSFT is supporting its partners use of Hypervisor Platform API. But again different issue from nested virtualization in root domain.
I will check if there is a matching issue on user voice when I have time. (Other’s contributions welcome).
For stability issues related to Vbox, feel encouraged to continue the discussion at the link you provided. Third party VM vendors are working closely with MSFT on these issues; they are being taken seriously.
There is an issue for nested virtualization scenarios over at #4193, which for the time being remains open.
For questions/suggestion about the hypervisor platform, see this user voice.
For broad discussion and commentary, reddit and twitter. Not because no one cares. Because they are better platforms for general discussion and commentary.
Note that this patch is not yet included in the September '20 release of VirtualBox, i.e. 6.1.14. I’ve tried a development release (download can be found here) which currently installs version 140491(aka 6.1.97) I for now I found the stability and performance a whole lot better than the “stable” 6.1.14 release. It’s definitely worth the try. I’m running a 64-bit Win10 Pro (1909) host with Intel CPU and Hyper-V enabled (for Docker). Inside my VM I’m running Ubuntu 18.04 LTS, KVM virtualisation, VMSVGA GPU and 3D enabled. Benchmarks: