id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host 5639,AMD-V not working: VERR_SVM_IN_USE -> update your BIOS/workaround available in SVN/3.1.4,palomino,,"Cpu: AMD AthlonIIx3 425. Motherboard: GA-MA78GM-US2H HostOS: Ubuntu 9.10 GuestOS: Windows 2003 (2 processors allocated) Virtualization is enabled in BIOS. When i upgraded to 3.1.0, it reported ""VT-x is not available. (VERR_VMX_NO_VMX)."" when i tried to start the guest os. 3.0.12 worked fine. Reinstall 3.1.0 can not fix the issue. Remove 3.1.0 -> install 3.0.12 -> remove 3.0.12 -> install 3.1.0 works. But if I restart the computer, I have to do that again. BTW: It did not happen on another computer with intel's cpu. '''Recommendations:''' * upgrade your BIOS if possible * remove the KVM modules (Linux host) 3.1.4 will contain a workaround for people with a broken BIOS and no option to update it.[[BR]] Set the VBOX_HWVIRTEX_IGNORE_SVM_IN_USE environment variable to true (''set VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true'' on Windows; ''export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true'' on Linux) This will tell !VirtualBox to ignore VERR_SVM_IN_USE and continue to use AMD-V. Note that this is a hack and dangerous if you run more than one hypervisor at the same time. '''USE AT YOUR OWN RISK.''' ",defect,closed,VMM/HWACCM,VirtualBox 3.1.0,fixed,AMD-V,,Windows,Linux