Good morning.
I am using the latest version 6.1.32
it always worked, from today I get the same error as this thread.
I checked in the bios the virtualization activation is ok I always get the same error, I don't know how to fix.
Thank you
https://i.postimg.cc/DyC4M3jT/Ridimensi ... 104203.jpg
Error message "Not in a hypervisor partition"
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Error message "Not in a hypervisor partition"
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
-
- Posts: 10
- Joined: 13. Jul 2010, 14:59
- Primary OS: MS Windows 10
- VBox Version: OSE other
- Guest OSses: Windows 10
Re: Error message "Not in a hypervisor partition"
- Attachments
-
- log virtual machine.rar
- (6.08 KiB) Downloaded 11 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Error message "Not in a hypervisor partition"
RAM overcommitted, and anyhow there's no way an 8GB PC running Win64 can afford to dedicate 4GB to a VM. Reduce VM RAM to 2GB. Consider adding RAM to the host if you want to run VMs of this size on it.00:00:03.896049 Host RAM: 8183MB (7.9GB) total, 4155MB (4.0GB) available
...
00:00:04.108729 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:04.108978 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
And VT-x is disabled in the host BIOS. See FAQ: I have a 64bit host, but can't install 64bit guests.00:00:04.109305 HM: HMR3Init: Attempting fall back to NEM: VT-x is disabled in the BIOS for all CPU modes
-
- Posts: 10
- Joined: 13. Jul 2010, 14:59
- Primary OS: MS Windows 10
- VBox Version: OSE other
- Guest OSses: Windows 10
Re: Error message "Not in a hypervisor partition"
Good morning.
I restored the OS image with version 6.1.30 and everything works fine, so I am attaching the log file.
The problem arises when I upgrade to version 6.1.32 I get the error I described above.
Even when uninstalling and reverting to the previous version (6.1.30) I always get the same error.
I don't understand where this latest version is causing problems on my operating system, but it certainly prevents it from working properly.
So I restored the OS image again with version 6.1.30 and everything works fine.
I really don't understand, I presume the latest version is not compatible with my obsolete hardware (i5 750)
I restored the OS image with version 6.1.30 and everything works fine, so I am attaching the log file.
The problem arises when I upgrade to version 6.1.32 I get the error I described above.
Even when uninstalling and reverting to the previous version (6.1.30) I always get the same error.
I don't understand where this latest version is causing problems on my operating system, but it certainly prevents it from working properly.
So I restored the OS image again with version 6.1.30 and everything works fine.
I really don't understand, I presume the latest version is not compatible with my obsolete hardware (i5 750)
- Attachments
-
- Log Virtual machine OK.rar
- (28.97 KiB) Downloaded 5 times
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Error message "Not in a hypervisor partition"
When you followed the link provided by mpack, did you read and follow the last post of the FAQ precisely (disabling all mentioned Windows component and using the bcdedit command)?
The background reason is that the error message can perhaps indicate a partially active Hyper-V on the Windows host.
The background reason is that the error message can perhaps indicate a partially active Hyper-V on the Windows host.