virtualbox.org

I had created several 64 bit guest VMs using VirtualBox-OSE (3.0.8_OSE r53138) on my AMD 240 based linux host, and they appeared to work OK. When I "upgraded" to VirtualBox (3.2.6), primarily to try attaching USB devices to the VMs, I got error messages saying "AMD-V enabled, but not working", and the VMs would not start. Reverting to VirtualBox-OSE gives me working 64 bit VMs again. What's up?

The version you 'reverted' to for the OSE, that was 3.0.8 again? If so, then it means that the new check introduced in 3.1 is giving you this error. Please check your BIOS and system for AMD-V (SVM) capabilities.

I know this bug:
http://www.virtualbox.org/ticket/5639

It is buggy BIOS on some AMD systems. VBox 3.1+ has blocked those BIOSes. VBox 3.0.x did not check BIOS quality.
Problem is not with OSE.

upg. BIOS -or-
try:
# killall VBoxSVC
# export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true
# VirtualBox

-Technologov

Sasquatch -Thanks for the prompt reply. Yes, reverted to 3.0.8_OSE. Bios has switch for "Enable SVM" which is enabled. 64 bit guest runs in 64 bit mode with 3.0.8_OSE. When I tried using 3.2.6, if I ignored the error message and hit continue, guest would not complete boot, claiming it was not on a 64 bit machine. Not sure what the "check" you mention was introduced for, but seems like there may perhaps be a bug in the newer VirtualBox as well (?).


Technologov - Thank you also for the swift reply. I will re-install VirtualBox 3.2.6, and try your recommended work-around. Sounds like this is just telling VirtualBox to ignore it's own check, no?

>Sounds like this is just telling VirtualBox to ignore it's own check, no?

Yes, it is.
For the long and detailed answer, look into bug #5639.

"the new check" is exactly what I told you about.

Technologov - Thanks again for your help. I should have read ALL the way through that bug report the first time. After doing so, I examined my system and found that (as a result of experimenting with a number of different approaches to virtualization) I had an old (and forgotten) copy of KVM still installed. Uninstalling that prior to reinstalling VirtualBox 3.2.6 resolved my problem, without resorting to the work around of defeating the check. Again, Thanks!