VirtualBox, AMD_V, and "recompile your kernel and reboot"
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. I've tried with both 3.10.11 and 3.11.2 from fedora. I am unable to see any kvm that is already running, and - more to the point - what causes kvm_amd to be loaded in the first place, since rmmod happily unloads what must be an unused module. Playing around a bit, VirtualBox says that it turns on the AMD-V option automatically if a 64-bit VM is selected. Btw, the .vdi was converted from the raw - a bootable usb stick with a full blown fedora OS on it. I can't see that having any relevance as the error comes up before any boot process has happened. Suggestions please - I can do a kernel recompile, but what I have to disable isn't clear.
Hi Allan Which version of Virtualbox is that? Is it a recent one? Recent ones seem handle KVM presence better. Older ones have trouble. There is an option to disable hardware virtualisation extension: Settings->System->Acceleration. Do you have this on? You dont need to disable KVM is you turn h/ware extension off. But this may not be what you want. Daniel On 08/10/13 11:01, Allan Duncan wrote:
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.
I've tried with both 3.10.11 and 3.11.2 from fedora.
I am unable to see any kvm that is already running, and - more to the point - what causes kvm_amd to be loaded in the first place, since rmmod happily unloads what must be an unused module.
Playing around a bit, VirtualBox says that it turns on the AMD-V option automatically if a 64-bit VM is selected.
Btw, the .vdi was converted from the raw - a bootable usb stick with a full blown fedora OS on it. I can't see that having any relevance as the error comes up before any boot process has happened.
Suggestions please - I can do a kernel recompile, but what I have to disable isn't clear. _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
On 08/10/13 11:15, Daniel Jitnah wrote:
Hi Allan
Which version of Virtualbox is that? Is it a recent one?
Recent ones seem handle KVM presence better. Older ones have trouble.
There is an option to disable hardware virtualisation extension:
Settings->System->Acceleration.
Do you have this on? You dont need to disable KVM is you turn h/ware extension off. But this may not be what you want.
Daniel
It doesn't work - if you want 64-bit you must have it, see below.
On 08/10/13 11:01, Allan Duncan wrote:
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.
I've tried with both 3.10.11 and 3.11.2 from fedora.
I am unable to see any kvm that is already running, and - more to the point - what causes kvm_amd to be loaded in the first place, since rmmod happily unloads what must be an unused module.
Playing around a bit, VirtualBox says that it turns on the AMD-V option automatically if a 64-bit VM is selected.
Btw, the .vdi was converted from the raw - a bootable usb stick with a full blown fedora OS on it. I can't see that having any relevance as the error comes up before any boot process has happened.
Suggestions please - I can do a kernel recompile, but what I have to disable isn't clear. _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
Hi Allan, You virtualbox version is too old, the current one is 4.2.18 Try download it from official site https://www.virtualbox.org/wiki/Downloadsor follow the guide here http://www.if-not-true-then-false.com/2010/install-virtualbox-with-yum-on-fe... Cheers, Bruce On Tue, Oct 8, 2013 at 11:01 AM, Allan Duncan <amd2345@fastmail.com.au>wrote:
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.
I've tried with both 3.10.11 and 3.11.2 from fedora.
I am unable to see any kvm that is already running, and - more to the point - what causes kvm_amd to be loaded in the first place, since rmmod happily unloads what must be an unused module.
Playing around a bit, VirtualBox says that it turns on the AMD-V option automatically if a 64-bit VM is selected.
Btw, the .vdi was converted from the raw - a bootable usb stick with a full blown fedora OS on it. I can't see that having any relevance as the error comes up before any boot process has happened.
Suggestions please - I can do a kernel recompile, but what I have to disable isn't clear. _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
-- simple is good http://brucewang.net http://twitter.com/number5
On 08/10/13 12:24, Bruce Wang wrote:
Hi Allan,
You virtualbox version is too old, the current one is 4.2.18
Bah Humbug. Instead of rushing off the the website to check, I just asked VirtualBox if it needed updating, and it told me I was up to date. You can't trust anyone these days. Anyway, updating to 4.2.18 doesn't make a difference.
Just checking, but is this AMD-V thing enabled in the BIOS? I've noticed on a few machines that some of the virtualisation options were disabled by default in BIOS, so it does happen. On 8 October 2013 11:01, Allan Duncan <amd2345@fastmail.com.au> wrote:
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.
I've tried with both 3.10.11 and 3.11.2 from fedora.
I am unable to see any kvm that is already running, and - more to the point - what causes kvm_amd to be loaded in the first place, since rmmod happily unloads what must be an unused module.
Playing around a bit, VirtualBox says that it turns on the AMD-V option automatically if a 64-bit VM is selected.
Btw, the .vdi was converted from the raw - a bootable usb stick with a full blown fedora OS on it. I can't see that having any relevance as the error comes up before any boot process has happened.
Suggestions please - I can do a kernel recompile, but what I have to disable isn't clear. _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
-- Turning and turning in the widening gyre The falcon cannot hear the falconer Things fall apart; the center cannot hold Mere anarchy is loosed upon the world
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.
participants (5)
-
Allan Duncan -
Bruce Wang -
Daniel Jitnah -
Toby Corkindale -
trentbuck＠gmail.com