It is kind of expected for 3rd party virtualization products not to work when Hyper-V is enabled, after all it's a type 1 hypervisor (native, like Xen or ESXi) and not a type 2 one (hosted, like VirtualBox or VMware Workstation). It's interesting that maybe VirtualBox has finally managed to fix the compatibility even without Microsoft's help using their proprietary intentionally broken APIs, but this might not be a long-lived solution and there is no sense in building any of your systems to depend now on Hyper-V since there are no guarantees it will not break again in the future.Īlso this is far from the only issue with Hyper-V, though it was the most significant one to my work. The links on that page also link to VirtualBox 6.0 changelog - and all versions of VirtualBox 6.0 still fail to work under Hyper-V. A page which still made invalid claims about 'recently both VirtualBox and VMware have released versions that support Hyper-V and WSL2' - out of date propaganda. If Microsoft breaks their APIs likely to intentionally break the compatibility with 3rd party virtualization software, how is that Oracle's fault?Īnd you linked to /en-us/windows/w. I don't defend Microsoft and how it is implementing hardware-accelerated virtualization in Windows, but they have architectural reasons for how they make hardware-accelerated virtualization available in Windows, even though I personally believe to pack Hyper-V with the higher-priced Enterprise and Pro editions while blocking any other access to the processor's hardware accelerated virtualization is some sort of robbery - almost every processor made and sold within the last decade enables some sort of hardware-accelerated virtualization. After all, the hypervisor runs in ring 0 of the processor and you would like to have a restricted and safe environment to manage such applications with care and caution, especially on Windows.! You can change VirtualBox' para-virtualization to Hyper-V. It's a feature Microsoft sells, true, but on the other hand it provides a layer of management and security for sysops to control when, what and how virtualization on a Windows system takes place in order to comply to ISO certification.

Hyper-V is a hardware abstraction layer, exclusively claiming your processor's virtualization and providing an API for Type-2-virtualizers running on Windows.

If you have issues booting a Linux ISO with a Hyper-V machine, try to switch 'Safe Boot' to 'Microsoft UEFI Certification Authority' and enable TPM.

Vmware player wsl2