virtualbox.org

Hi,
I have been using virtualbox for years very successfully. However its just stopped working and I can't work out why. I get the error as attached
"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)."

I haven't made any changes in BIOS before this has occurred and have been using the same template image to create machines for ages. My template image with Win 10 etc setup won't start either.

From my trouble shooting/reading I have confirmed in BIOS Intel Virtualization technology is enabled. To make sure I have turned this off powered down and turned on again powered down and booted still to no avail. I have even set Paravirtulization interface to none (in settings->system->acceleration) and the virtual machine still won't turn on.

I have checked Hyper-V is unticked in the windows features control.

System Details:
-Host Windows 10 Pro 21H2,build 19044.1526, 64bit. 32gb ram
-Virtual machine Win 10 64bit.

Running out of ideas, any help is very much appreciated. Thanks.

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

Hi, Thanks, uploaded log as requested.

More system details (I know its getting a bit old but use to work fine):
Intel Core i7-3930K
ASUS RAMPAGE IV EXTREME
AMD Radeon HD 7970/R9 280X

Thanks for the log.

Unfortunately it says the same thing as the error dialog.

00:00:04.373985 HM: HMR3Init: Attempting fall back to NEM: VT-x is disabled in the BIOS for all CPU modes
00:00:04.374215 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1460) int __cdecl nemR3NativeInit(struct VM *,bool,bool); rc=VERR_NEM_NOT_AVAILABLE
00:00:04.374248 VMSetError: Not in a hypervisor partition (HVP=0)
00:00:04.374270 NEM: NEMR3Init: Native init failed: VERR_NEM_NOT_AVAILABLE.

The error message seems quite definitive: VT-x is disabled in the BIOS. Please note that if you go into the BIOS and see something called VT-d, that is not the same thing. Also you may need to power down the PC and restart for VT-x changes to take effect.

Have you installed any third party system level tools recently? E.g. non Microsoft antivirus, some kind of debug tool or system emulator?

Thank you for your help. I can't think of anything that I have installed. I use AVG antivirus. I will remove it, reboot and try again.

From motherboard manual:
"Intel Virtualization Tech [Enabled]
[Enabled] Allows a hardware platform to run multiple operating systems separately
and simultaneously, enabling one system to virtually function as several
systems.
[Disabled] Disables this function."

Its enabled (as described further above) - presume this is the only thing I need to check in BIOS or have I missed something?

Under windows features I see "virtual machine platform" is unticked - is this needed or will take over the virtualization service?

WOW - much to my disbelief after uninstalling AVG Virtualbox works! Something must have changed in one of its updates. I will put it back in and look closer at the options in its config.

For anyone else that has this problem I seen in AVG forum I am not the only one.

Go to menu>settings>troubleshooting, then, under "enable hardware-assisted virtualization" uncheck

Thanks very much for your help.

Andrew

I'm glad you got to the bottom of it. Most of us around here is that Microsoft are the experts on how to write Windows system code without messing up apps, therefore we do not recommend third party AV, most of which is (frankly) very close to snake oil.

And no, you do not have to enable Hyper-v to get VirtualBox VMs to run. Quite the contrary: while attempts are being made to make the two systems tolerate each other better, for the moment VirtualBox always runs way, way better if Hyper-v is totally disabled.