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

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Fielding
Posts: 170
Joined: 3. May 2012, 22:21

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

Post by Fielding »

Host : Windows 10 home
I can't initialize any VM.

Message :
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}

If you need additional information please ask
Best Regards
Last edited by Fielding on 8. Jun 2021, 21:51, edited 1 time in total.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

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

Post by mpack »

Fielding
Posts: 170
Joined: 3. May 2012, 22:21

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

Post by Fielding »

Thanks mpack. I will try and comment.
Best Regards
Fielding
Posts: 170
Joined: 3. May 2012, 22:21

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

Post by Fielding »

I don't have guests in 64 bits. Only the host.
My problem is born in this way :
I restore the host system windows 10 home from one of my pc's to another. All goes well, but now I can't open the virtual machines under that system. They are install in a data disk.
So I think my problem is related to this.

Best Regards
Fielding
Posts: 170
Joined: 3. May 2012, 22:21

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

Post by Fielding »

The prior windows host system was windows 8.1
I use the same virtualbox configuration in all my pc and laptops.
Best Regards

The VM menu list is recognize without problem.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

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

Post by mpack »

Fielding wrote: I don't have guests in 64 bits. Only the host.
Read the FAQ.
Fielding
Posts: 170
Joined: 3. May 2012, 22:21

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

Post by Fielding »

I have decided uninstall virtualbox and install again.
I will create again the environmental variables.
If you want to know more read the FAQ.
Best Regards
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

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

Post by scottgus1 »

Fielding wrote:I have decided uninstall virtualbox and install again.
This will not fix the problem in the first post.
Fielding wrote:I will create again the environmental variables.
"environmental variables" often refers to the environment variables used by the Windows command line, like PATH and TEMP. Setting these will also not fix the problem in the first post.

Following the posted FAQ will fix the problem in the first post, if your new host PC can be fixed.

Have you read the FAQ? Are you having trouble understanding it?
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

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

Post by scottgus1 »

Fielding I moved your last post here to "Feedback to the Moderators". That is the place for your last post, please see my response. viewtopic.php?f=9&t=8888&p=500875#p500875

Here, you can please relate what part of the FAQ you did not understand, or that you solved the problem.
Fielding
Posts: 170
Joined: 3. May 2012, 22:21

Re: [Solved] Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

Post by Fielding »

I decided to begin investigating this :
"VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)"

I enter the BIOS uefi type.
In Advanced - CPU configuration I locate these entries

Intel VT-x Thchnology - Supported
Intel Virtualization Technology --- Disabled

and in Advanced - system agent (SA) configuration

VT-d capability ----- Disabled
CFG Lock ----- Disabled

I decide to risk and change some of those items
I enable Intel Virtualization Technology
I enable VT-d capability

That seems to solve completely my problem in the first proofs .
Any incidence I will comment.

I was preparing the total reinstallation of VirtualBox because this pc already hace VB in the past under windows 8.1. Now with the acronis special restore was with windows 10 home .
So I thought is not was the BIOS, but then I remember I update the BIOS during the acronis restore too.

So that may be the cause of the disconfiguration.

I also have another minor problem in the first time. When I shutdown the pc don't obey and reinitate. I lost the control of the pc and cannot boot so I try with external tools. I recover the system and observe that changing in the BIOS another feature shutdown correctly. A little slowly at the present moment. I am investigating why, because the system goes well in safe mode.
So probably is a drive.

I will continue my investigations in others forums. The Virtualbox problem is solved.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: [Solved] Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

Post by scottgus1 »

Fielding wrote:Intel VT-x Thchnology - Supported
Intel Virtualization Technology --- Disabled
...
I enable Intel Virtualization Technology
This was the right thing to do. Glad you found it!
Fielding wrote:I enable VT-d capability
This one won't hurt, but it doesn't help Virtualbox either. Enabling VT-x was the setting needed.
Post Reply