Allan Duncan <amd2345@fastmail.com.au> writes:
I have VirtualBox up and running fine with a 32-bit XP image, but when I tried to configure a 64-bit linux machine VirtualBox barfs when you try to start it with:
Failed to open a session for the virtual machine linux_test. 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).
Searching for this found a match, but their solution of rmmod kvm_amd kvm I had already tried with modprobe -r and it doesn't fix it anyway.
In /etc/modprobe.conf.d/foo.conf add blacklist kvm if it's being loaded by hand, or install kvm /bin/false if it's being autoloaded. Then reboot. That should prevent the kvm module being loaded. (From memory -- path and module name may be wrong. It's *not* /etc/modules.) PS: vbox is stinky poo that's only useful for yukky GUI stuff. kvm is much better.