VirtualBox 6.0 and Hyper-V

[socratis]

'odbayar',
Since your reply came right after my post, I'm assuming you're referring to my post. I am not Oracle. I do not have any channels with Microsoft. I'm just a simple user just like you...

[nsteblay]

Is it worth trying to get Virtualbox working on Windows 10? It looks like many are having the Call to VidMessageSlotMap failed: Last=0xc000000d/87 (VERR_NEM_VM_CREATE_FAILED error with no obvious resolution.

[nathaniel515]

If using the ring 0 runloop is a (now-broken) hack, why doesn't VirtualBox disable it by default? It's not improving performance if it stops everything from working...

[jruhe]

Gerhart,
They briefly worked when MS published their API with 1809, but they broke it with 1903 and they really nuked the place with 1909.

In release 2004 something will change angain, because Vmware officially announced hyper-v support.
https://blogs.vmware.com/workstation/20 ... -20h1.html

jruhe

[Gerhart]

Microsoft hope, that VirtualBox will be working with Hyper-V in future.
https://twitter.com/vBenArmstrong/statu ... 2305601536

But we still don't hear from VirtualBox developers, what exactly they need from Microsoft for good VirtualBox performance: kernel API analog of Windows HV platform, 1-2 documented callbacks to Hyper-V virtual CPU scheduler or something else...

[BillG]

The changelog for Version 6.1.4 claims that the ability to run VirtualBox with Hyper-V enabled has been restored, and in fact it has.

I upgraded my machine running Windows 10 Version 2004 (Build 19041.84) to VirtualBox 6.1.4 and checked that my Windows 7 guest ran OK. I then installed Hyper-V and tried my vm again. It started and booted to the Windows 7 Starting Windows screen with the green turtle icon showing. Some time later it is still at the same spot but has not crashed. Task Manager shows the VIrtualBox Virtual Machine running and using about 29% CPU.

It is certainly not usable yet but it does at least run, not abort.

VBoxT.PNG

[klaus]

Yes, what 6.1.4 effectively does is disabling the (apparently no longer working, probably needs to be improved) optimization which avoids going always to usermode. We couldn't find time to work on restoring the functionality of the optimization, so we had to give in for now. We also couldn't investigate the new improvements available in 20H1 (preview only so far) which apparently VMware is providing a test version for.

[BillG]

Thanks. At least the vm loads, so users will see the Green Turtle rather than an obscure message from the host OS, so the cause will be obvious.

[rsrx]

Thanks for working on this. I have Windows 10 v2004 and with latest VirtualBox it seems that vagrant is able to boot up Ubuntu machine but it halts halfway through. Is there any ETA on when this will be fully supported?

[evil_gr]

Hi everyone!

I try to run Ubuntu x64 using VirtualBox 6.1.4 r136177 on Windows 10 build 1809 with enabled Hyper-V, and it seems to me that there is a bug - I've found something interesting in the startup log:

Code: Select all

00:00:03.206187 VMSetError: F:\tinderbox\win-rel\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1301) int __cdecl nemR3NativeInit(struct VM *,bool,bool); rc=VERR_NEM_MISSING_KERNEL_API
00:00:03.206189 VMSetError: VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API
00:00:03.206204 NEM: NEMR3Init: Native init failed: VERR_NEM_MISSING_KERNEL_API.
00:00:03.206212 VMSetError: F:\tinderbox\win-rel\src\VBox\VMM\VMMR3\HM.cpp(622) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_NO_VMX
00:00:03.206216 VMSetError: VT-x is not available
00:00:03.335027 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API (VERR_NEM_MISSING_KERNEL_API).

Looks like an uncaught exception or unexpected behavior. You can find the full log in the attached file.

[klaus]

That's a very strange issue - you're running Windows 10 1809, and this has been reported to be working by others. I wonder if there are API availability differences between the Windows 10 editions, i.e. Home/Pro (and maybe the S mode also has an effect).

What's really odd is that the failing check is in the vbox kernel part, and this shouldn't be used any more with 6.1.4.

[yawnmoth]

I'm running VirtualBox 6.1.4 and when I try to open up a VM I get the following error:

Failed to open a session for the virtual machine vagrant_default_1583698990398_29087.

VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API (VERR_NEM_MISSING_KERNEL_API).

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I thought VirtualBox was supposed to play nice with Hyper-V as of 6.0. What gives?

[BillG]

Hyper-V is not the only app which can lock hardware virtualisation. There are a host of Windows and third party apps which can do this, and there is no "magic bullet" fix. You just have to find what it is by trial and error.

To say that Hyper-V and VirtualBox 6.0/6.1 "play nice" is an overstatement. As klaus said in his post a few posts back, all they have done in version 6.1.4 is disable the optimisation which was causing serious problems. We are back to the stage where it doesn't abort before loading. It loads and displays the green turtle icon below the screen, but does not actually do anything useful after that.

The only way to satisfactorily run VirtualBox version 6.1.4 on Windows 10 at present is to prevent the Hyper-V hypervisor from loading and remove any other app which locks hardware virtualisation to itself.

In addition, this forum does not support vms running under Vagrant.

[Larswa]

Hyper-V is not the only app which can lock hardware virtualisation. There are a host of Windows and third party apps which can do this, and there is no "magic bullet" fix. You just have to find what it is by trial and error.

To say that Hyper-V and VirtualBox 6.0/6.1 "play nice" is an overstatement. As klaus said in his post a few posts back, all they have done in version 6.1.4 is disable the optimisation which was causing serious problems. We are back to the stage where it doesn't abort before loading. It loads and displays the green turtle icon below the screen, but does not actually do anything useful after that.

The only way to satisfactorily run VirtualBox version 6.1.4 on Windows 10 at present is to prevent the Hyper-V hypervisor from loading and remove any other app which locks hardware virtualisation to itself.

In addition, this forum does not support vms running under Vagrant.

What do you mean by "the forum does not support vms running under vagrant" ?

HyperV and virtualbox 6.1.4 vagrant machines are running fine on my machine. An Amd Ryzen 3900. Performance for my usage ... Testing local infrastructure Ansible Scripts ... are okay. I dont see any difference between running vb natively without hyperv running, but the new cpu might hide the fact that it is wildly inefficient underneath

https://photos.app.goo.gl/W2i7WXniSP75mHFC8

[mpack]

What do you mean by "the forum does not support vms running under vagrant" ?

It means exactly what Bill said. We don't support Vagrant here, only the official VirtualBox install. That doesn't mean it won't work, it means take your support questions to the Vagrant forum.