VT-X/AMD-V enabled but not operational

[joeller]

I had a Dell 6510 with a windows 7 64 bit OS on it. I installded Virtual Box and install a VM which I had created on the 64 bit machine at work which has a windows server 2003 OS 64 bit OS installed on it . VM system setting shows VT-X/AMD-V enabled.

That machine died when for some reason it could no longer find the hard drive. I was provided with a new machine a Dell 6500 with an Intel Core 2 Duo P8600 CPU. This machine had Windows 7 32 bit installed on it. According to my lookups on the interet, this processor is 64 bit capable.

The Virtual box FAQs state that a 32 bit host can run 64 bit guest if virtualization is enabled in the bios. So I opened the bios, and enabled "Dell virtualization technology". I then rebooted opened Virtual box and tried to start the Virtual machine and still got "VT-X/AMD-V is enabled but not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot."

I am at a loss. What am I to do now?

[mpack]

Please provide a VM log file so I can be sure about the error - see Minimum information needed for assistance.

Often there are two virtualization settings in the host BIOS, I can't give you exact names but one is for enabling Virtualization Technology (VT-x), and if it exists then the other enabled Virtual I/O redirection (VT-d). It's the former that you need to run 64bit VMs. Check with your BIOS manufacturer if you aren't sure what the correct setting is.

In addition to the host BIOS, you need to make sure that no other application is already using VT-x. Typical culprits include Hyper-V, or debuggers, some antivirus apps may use it. However I wouldn't have expected these to be an issue if you only just now enabled the VT-x feature in your BIOS.

[joeller]

I added the most recent vbox.log file. Vbox.log.1, vbox.log.2 and vbox.log.3 will not load because web site says extension ".1" is not allowed. I tried to change the extension while loading it but that did not work either. so I copied and renamed the files to Vbox-1.log etc. I don't know if this will be readable. It would not allow me to load thevbox.log.3 files saying that three files is the maximum.

I tried to create a new VM as a windows 7 32-bit OS VM showing the VDI as the hard disk. But it still tried to open the Windows server 2003 -64 OS. So I don't know which log file contains my intial problem.

I enabled both Virtual Technology and Virtual I/O settings in the BIOS. Then I tried with just Virtual Technology enabled.

[mpack]

Only one log is required.

Ok, the log confirms that you identified the CPU correctly and that the error code is VERR_VMX_MSR_LOCKED_OR_DISABLED. That means is isn't enabled in your host BIOS, or something else has locked it for its own use. Only you can track down a definite answer.

[joeller]

OK I open the bios again and clicked restore defaults. then restarted. Still same error. I open bios again this time clicked Intel Vitual Technology ONLY without the Vitual I/O. I then booted up and started the VM this time itopened normally.

So apparently, if you select VT I/O then it locks up VT-X. So anyone else reading this, don't do that.

[michaln]

So apparently, if you select VT I/O then it locks up VT-X. So anyone else reading this, don't do that.

That sounds like a BIOS bug (wouldn't be the first one).

[joeller]

It's what I've cometo expect of Dell Crap.