virtualbox.org

Good morning
I've just upgraded VB and receive the following error-

Failed to open a session for the virtual machine CADsoft Build.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

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

Is there a possible fix please?
Cheers
Matt

See related FAQ. FAQ: I have a 64bit host, but can't install 64bit guests.

Ok, so I found a very thorough response already in the VB forum in response to my issue as per link-

viewtopic.php?f=1&t=62339

I went through each item and found that all settings were already as recommended.
I therefore tried to ENABLE Hyper-V. And to my surprise VirtualBox is up and running again...

The following was my guide to turn on Hyper-V-
1. Press Windows key + X and select Apps and Features.
2. Scroll down to the bottom and click Programs and Features link.
3. Then click the Turn Windows features on or off link on the left pane.
4. Locate Hyper-V option and unmark it.
5. Click OK to save the changes and reboot.

NOTE- I have a 64bit host (Windows 10) & 32bit guest (Windows 7)

Matt_Stengert wrote:Ok, so I found a very thorough response already in the VB forum in response to my issue as per link-

viewtopic.php?f=1&t=62339

You mean the link that Mpack posted to you above your post? It's a good idea to read and acknowledge what others have written.

Matt_Stengert wrote:I therefore tried to ENABLE Hyper-V.

Matt_Stengert wrote:4. Locate Hyper-V option and unmark it.

Did you enable or disable? Unmarking is disabling.

FWIW, the combination of VERR_VMX_MSR_ALL_VMX_DISABLED and VERR_NEM_NOT_AVAILABLE can mean two things. Either VT-x is disabled in the BIOS, or Hyper-V is in some sort of state where it hides VT-x from VirtualBox, but doesn't provide the NEM interface to VirtualBox.

In the former case, the obvious solution is to enable VT-x in the BIOS.

In the latter case, both disabling and enabling Hyper-V can solve the issue, but a VirtualBox VM will usually be faster in VT-x mode than in NEM mode.

mpack wrote:See related FAQ. FAQ: I have a 64bit host, but can't install 64bit guests.

My apologies "mpack", I hadn't noticed the link you provided, thank you!

scottgus1 wrote:

Matt_Stengert wrote:Ok, so I found a very thorough response already in the VB forum in response to my issue as per link-

viewtopic.php?f=1&t=62339

You mean the link that Mpack posted to you above your post? It's a good idea to read and acknowledge what others have written.

Matt_Stengert wrote:I therefore tried to ENABLE Hyper-V.

Matt_Stengert wrote:4. Locate Hyper-V option and unmark it.

Did you enable or disable? Unmarking is disabling.

Sorry "scottgus1", I marked it...I had a shocker losing a whole day of business whilst rectifying the issue. I should have been more attentive.
Cheers

fth0 wrote:FWIW, the combination of VERR_VMX_MSR_ALL_VMX_DISABLED and VERR_NEM_NOT_AVAILABLE can mean two things. Either VT-x is disabled in the BIOS, or Hyper-V is in some sort of state where it hides VT-x from VirtualBox, but doesn't provide the NEM interface to VirtualBox.

In the former case, the obvious solution is to enable VT-x in the BIOS.

In the latter case, both disabling and enabling Hyper-V can solve the issue, but a VirtualBox VM will usually be faster in VT-x mode than in NEM mode.

Thank you "fth0", that seems to make sense. Locating the VT-x in the BIOS was the one thing I was unable to do.
Cheers