Different versions of VirtualBox and Hyper-V

[ccicnce113424]

Operating system: Windows 10 1909 (Hyper-V enabled)
Error message on VirtualBox 6.0.22:

Code: Select all

Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

on VirtualBox 6.1.6:

Code: Select all

VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API_2 (VERR_NEM_MISSING_KERNEL_API_2).
VT-x is not available (VERR_VMX_NO_VMX).

I really hope that one day the latest version of VirtualBox will actually use Hyper-V interface.

[multiOS]

It does but usually very, very slowly, and success is patchy; and according to the warning in the VirtualBox User Manual it may be highly dependent on having the 'right' blend of hadware, whatever that may be. I have managed to get it working on a Microsoft Surface Book 2, but haven't had time to do any extensive testing yet; and I'm fully prepared for it to stop working again when Microsoft releases its next version update!

[multiOS]

Working Example: Image attached.

Would I trust the VirtualBox VM for serious work? Absolutely NOT - Would describe the level of success as 'Alpha' quality rather than 'Beta', but not bad for both Hyper-V Windows 10 and VirtualBox Windows 10 VM actually running simultaneously.

[ccicnce113424]

WSL2, Windows Sandbox, Docker and Android Studio requires Hyper-V. VMWare 20H1, qemu for windows also support Hyper-V. I think it's very important for VBox to support it.

[scottgus1]

I think it's very important for VBox to support it.

So do the devs, because so do the paying Oracle customers.

We on the forum would probably like it too, so this whole "why doesn't Virtualbox work with Hyper-V" brouhaha can blow over...