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 > [email protected] > http://lists.luv.asn.au/listinfo/luv-main _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
