virtualbox.org

I have virtualbox working fine on a Windows 10 Home host.
Trying to set it up on another host PC with Windows 10 Pro.
I am getting the following error when I try to start the Virtual Machine:
Attached is the log file for that machine in a zip file.
VTx is enabled in the BIOS
"Virtualization Technology Directed I/O (VT-d2)" is enabled in the BIOS.

"Windows Hypervisor Platform" is checked/enabled in the windows features.
"Virtual Machine Platform" is checked/enabled in the windows features.
"Hyper-V" is disabled/unchecked in the windows features.
(I had once enabled hyper-v, but then I disabled it after getting this error. Still get the error though)

I read that if hyper-v is enabled it could cause this problem. But I have it disabled in the windows features menu. Is there somewhere else where I need to disable it?
Any ideas what I should try?
Thanks.

HOST PC SPECS: 2x Intel Xeon X5570 (4cores,4threads each), 24GB RAM, Nvidia NVS 510

Please see HMR3Init: Attempting fall back to NEM (Hyper-V is active).

caleb1 wrote: VTx is enabled in the BIOS.

Not according to the log you provided.

Btw, VT-d is not required. Only VT-x.

If you just turned VT-x on then be aware that you need to fully power down the PC after and restart.

On your host, open a command prompt, execute the following commands and provide the results:

---

mpack wrote:

caleb1 wrote:VTx is enabled in the BIOS.

Not according to the log you provided.

This conclusion is not necessarily correct. Let me elaborate:

1) VirtualBox first checks the CPU capabilities using the CPUID command. If the CPU doesn't support VMX, MSR or FXSR, VirtualBox throws the VERR_VMX_NO_VMX error. This often happens if another hypervisor (or software) intercepts the CPUID command, just like VirtualBox does inside its guests.

2) In a second step, VirtualBox checks the IA32_FEATURE_CONTROL MSR. If enabling VT-x is not allowed, VirtualBox throws one of the VERR_VMX_MSR_VMX_DISABLED or VERR_VMX_MSR_ALL_VMX_DISABLED errors. This usually happens when VT-x is disabled in the BIOS, which sets the Lock bit of the IA32_FEATURE_CONTROL MSR to disable VT-x.

The requested CPUID results will probably reveal more ...

scottgus1 wrote:Please see HMR3Init: Attempting fall back to NEM (Hyper-V is active).

Doing all the steps from this above link fixed the problem.

Thank you very much!

Great! Glad you're up and running.