On Saturday 03 April 2010, sdavmor wrote:
> Hardware: AMD Phenom 4 core processor, 8gb ram. Gigabyte motherboard
> < a year old (GA-MA790X-DS4).  Hardware virtualization switches are
> "on". Running the 2.6.32-19-generic kernel on a fully up to date Lucid
> Lynx (as of this morning). I can start my VBox 3.1.4 in single core
> mode after disabling AMD-V.
>
> VirtualBox - Error
> Failed to start the virtual machine Win2KOEM.
> AMD-V is being used by another hypervisor. (VERR_SVM_IN_USE).
> VirtualBox can't enable the AMD-V extension. Please disable the KVM
> kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE).
>
> Details
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}
>
> I do not have another hypervisor running. VBox is the only virtual
> machine I've ever used on this computer. I've checked in synaptic --
> no KVM or QEMU or VMWARE in use.
>
> Any constructive thoughts?

Might be a BIOS bug but make sure that no KVM modules are loaded
(lsmod | grep kvm). You could update VBox to version 3.1.6 and try
the following hack:

  export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=1
  VirtualBox ...

But again, don't do this if any KVM module is loaded.

Kind regards,

Frank
-- 
Dr.-Ing. Frank Mehnert

Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten
Amtsgericht München: HRB 161028
Geschäftsführer: Thomas Schröder

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community

Reply via email to