virtualbox.org

I cannot use it, I receive a msg "AMD-V is being used by another hypervisor" when I specify it for my Linux guest (see image). I don't have another hypervisor running (as far as I know )

My environment: Windows 32-bit host, Linux 32-bit guest, VB 3.2.8, AMD-V activated in BIOS. I would like to use HW acceleration for performance and because I would like to give more than one processor to the guest machine. Thank you in advance for your help.

http://imgur.com/db4eF.png

So you're saying you don't have VMWare or Virtual PC installed and running when you start the VM? Is there a BIOS update available for your motherboard? It would seem that it's a bug in the BIOS, or you are already running another VM in the background. Another possibility is that you have another program that somehow needs hardware accelerated virtualisation.

I don't have neither VMware, nor Virtual PC and no program requiring hardware accelerated virtualization. I have a recent motherboard but not the latest BIOS, maybe updating BIOS could help but the error message is misleading. I'll give it a try but not immediately. Thank you for your suggestion.

Sasquatch wrote:So you're saying you don't have VMWare or Virtual PC installed and running when you start the VM? Is there a BIOS update available for your motherboard? It would seem that it's a bug in the BIOS, or you are already running another VM in the background. Another possibility is that you have another program that somehow needs hardware accelerated virtualisation.

I have updated the BIOS to the latest non beta version and NOW IT WORKS !! Thank you for your kind help.

It seems to me that the message was misleading. My guess is that hardware virtualization was not available and the system assumed it was in use and sent a message to indicate that, when in fact it just had not been enabled by the old BIOS.

BillG wrote:It seems to me that the message was misleading. My guess is that hardware virtualization was not available and the system assumed it was in use and sent a message to indicate that, when in fact it just had not been enabled by the old BIOS.

You are probably right: the error messages have frequently to be "interpreted". If they were always correct life would be too easy

No, your BIOS just messed it up completely and set the in-use flag. For some BIOS manufacturers it's apparently difficult to read the specs and perform some simple steps correctly.