VERR_NEM_VM_CREATE_FAILED after Activating Hyper-V features in Windows 10

[mir82517]

Hi,

I am running several Virtual Machines in VirtualBox 6.0.8. I have installed the latest Windows 10 Version 1903 (Build 18362.145) with all patches.

After activating the Windows Features for Hyper-V (Hyper-V and Windows Hypervisor Platform) the VMs in VirtualBox will not start anymore.

The following error message appears, regardless of the guest operating system:

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).

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

It is not an option to deactivate the Hyper-V features because it is used within the company! Should we migrate all VMs to Hyper-V?

Best regards

Mathias John

[J.casselli]

hello, i have the same problem with the same interface : IConsole {872da645-4a9b-1727-bee2-5585105b9eed} (the hexa code is the same)

[LMS23]

I have the same problem. After activating Hyper-V, the VBox VMs no longer work. I've migrated the most important VMs to Hyper-V and I'm using it now.

[Socratis]

Duplicate of #18536.

[TruePhoenyx]

I know this is a Duplicate but it needs to be looked at.

Failed to open a session for the virtual machine H-V Test.

(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}

This is running on Hyper-V enabled machine. It needs to be pointed out that a lot of VBox VMs on Windows are to allow Linux to be run and with the upcoming WSL 2 and it's capabilities a good many of those people will move to it. A lot of companies that uses both are going to require the move to provide a homogenious enviorment. If Oracles VBox causes problems then it's going to be removed. And this is bad because there are a lot of VBox VMs that don't have Hyper-V equivalents. I've been told that VBox can run on top of Hyper-V as long as it's 6+, but I have had no luck getting it to run. I have 128GB of RAM so I know that's not the issue. Please help with this.

[Socratis]

Replying to TruePhoenyx:

I know this is a Duplicate but it needs to be looked at.

When something is marked as a Duplicate, you go to the Original ticket, you don't continue the discussion on the Duplicate.

In your case, it's not even a Duplicate, or belong to this ticket, you're not getting a VERR_NEM_VM_CREATE_FAILED error, you're getting a VERR_NEM_MISSING_KERNEL_API error, not the same. In your case it most probably means that you don't have an updated host.

Please help with this.

Head to the ​VirtualBox forums, a lot more eyes there. In the ​VirtualBox on Windows Hosts section of the forums you'll find plenty of similar results. If you can't locate one (maybe you didn't search enough?), open a new thread.

[LMS23]

Replying to socratis:

Replying to TruePhoenyx:

I know this is a Duplicate but it needs to be looked at.

When something is marked as a Duplicate, you go to the Original ticket, you don't continue the discussion on the Duplicate.

In your case, it's not even a Duplicate, or belong to this ticket, you're not getting a VERR_NEM_VM_CREATE_FAILED error, you're getting a VERR_NEM_MISSING_KERNEL_API error, not the same. In your case it most probably means that you don't have an updated host.

Please help with this.

Head to the ​VirtualBox forums, a lot more eyes there. In the ​VirtualBox on Windows Hosts section of the forums you'll find plenty of similar results. If you can't locate one (maybe you didn't search enough?), open a new thread.

By now it should be clear that the bug is due to VirtualBox in conjunction with a Hyper-V enabled Windows.

The question now is only if VirtualBox or Oracle has an interest to fix the problem or not.

socratis only refers to tickets or accuses of not having searched enough, this is a defensive attitude. Ok but not goal leading.

If no support for VirtualBox on Hyper-V enabled Windows is offered here, VirtualBox on Windows systems will disappear sooner or later.

[Socratis]

Replying to LMS23:

By now it should be clear that the bug is due to VirtualBox in conjunction with a Hyper-V enabled Windows.

You almost got it right... The trick with VT-x is that it has to be shared, since there's "only one" available slot for its use. For example, VMware and VirtualBox do not use VT-x at the same time, but rather take turns. To put it simply, every program that uses VT-x should do this: "VT-x lock" / "execute privileged code" / "VT-x unlock". This way other processes can use VT-x in turns.

On the other hand, Hyper-V permanently takes over VT-x and doesn't let anyone else use it. If a program uses VT-x from the moment it is loaded, and doesn't let go till the moment it dies, you have a problem. So, please complain to Microsoft about that.

The question now is only if VirtualBox or Oracle has an interest to fix the problem or not.

Microsoft has exposed an API that 3rd party virtualization solutions can call. This happened after Win10-1809, i.e. after Sep/2018. This is a relatively new API (not even a year old) and it's neither mature, nor optimized. You could use VirtualBox with Hyper-V being enabled after VirtualBox 6.0.0, but it's slower than molasses in the winter. Take a look at the following thread in the forums for some successes/failures: ​VirtualBox 6.0 and Hyper-V.

socratis only refers to tickets or accuses of not having searched enough, this is a defensive attitude. Ok but not goal leading.

I never would have thought that pointing to the obvious would be considered "defensive attitude". Asking people to do some searching and do their homework? Oh the heresy!

If no support for VirtualBox on Hyper-V enabled Windows is offered here, VirtualBox on Windows systems will disappear sooner or later.

Not sure where/how you came up with that conclusion, but I can't stop you from assuming/believing specific theories...

[janitor]

#18536