Page 1 of 1

VT-x/AMD-V hardware acceleration is not operational

Posted: 11. Aug 2012, 23:00
by CyberPine
Gateway DX4300 AMD Phenom II x4 810 Processor 2.60GH AMI 2.61 Bios with AMD-V enabled running Windows 7 x64 pro host.

I attached a windows 2003 32 VHD i had running on MS Virtual Host 2005 with no problems.

Attempt to create and install a Windows 7 pro x64 guest from install media in ISO format on an USB drive but I get:

VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.
Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer
.

I confirmed AMD-V is enabled on my Bios.

BIOS update maybe?

Did try to search on here first..

Thanks in Advance.

Re: VT-x/AMD-V hardware acceleration is not operational

Posted: 11. Aug 2012, 23:36
by Perryg
Is xp mode, hyper-v, or some other virtualizer on the host?

Re: VT-x/AMD-V hardware acceleration is not operational

Posted: 12. Aug 2012, 00:26
by CyberPine
Perryg wrote:Is xp mode, hyper-v, or some other virtualizer on the host?
Actually Yes. Windows Virual Server 2005 is installed. Not sure if that is a virtualizer.

Re: VT-x/AMD-V hardware acceleration is not operational

Posted: 12. Aug 2012, 00:41
by Perryg
Since only one VMX aware device can be run at one time that is why you are having issues trying to run a 64-bit guest with VirtualBox. VirtualBox was designed to *not* attach to the VT-x/AMD-v process if not actually running, but Windows really doesn't care about anything else than Windows so they attach at boot. You would need to disable the service before you can actually attach and run a 64-bit guest. Not sure you can actually do this with Windows Virual Server 2005 since that is what it was designed for.

Re: VT-x/AMD-V hardware acceleration is not operational

Posted: 12. Aug 2012, 01:01
by CyberPine
Perryg wrote:Since only one VMX aware device can be run at one time that is why you are having issues trying to run a 64-bit guest with VirtualBox. VirtualBox was designed to *not* attach to the VT-x/AMD-v process if not actually running, but Windows really doesn't care about anything else than Windows so they attach at boot. You would need to disable the service before you can actually attach and run a 64-bit guest. Not sure you can actually do this with Windows Virual Server 2005 since that is what it was designed for.
That worked! Thank you very much.