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