https://bugzilla.novell.com/show_bug.cgi?id=460042 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=460042#c2 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jnelson-suse@jamponi.net | --- Comment #2 from Jon Nelson 2008-12-18 06:07:54 MST --- I am not. kvm and kvm-kmp-default. I had already tried this: rmmod kvm-intel rmmod kvm modprobe kvm-intel which is what I do every time the module is upgraded. I get this on modprobe (that's all, no other messages): loaded kvm module (kvm-78-11.1) and this in the console when I run "qemu-kvm -k en-us -m 512 -hda ..." kvm_create_vm: Device or resource busy Could not create KVM context The previous package worked fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=460042 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=460042#c4 --- Comment #4 from Jon Nelson 2008-12-18 23:16:47 MST --- a reboot seemed to solve things. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=460042 User novellbmw@lsmod.de added comment https://bugzilla.novell.com/show_bug.cgi?id=460042#c6 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novellbmw@lsmod.de Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #6 from Bernhard Wiedemann 2009-01-03 23:31:00 MST --- I managed to reproduce a very similar behaviour on my Phenom X4 running OpenSUSE-11.1 with kernel 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux After the system starts, qemu-kvm works fine until I start a VirtualBox-2.0.6 (PUEL version from sun) guest. I verified that this guest has VT-x/AMD-V disabled. I also unloaded the vboxdrv kernel component afterwards, I tried to rmmod and modprobe the kvm_amd and kvm modules, but the only way to get kvm back to work was a reboot. This might be an issue with virtualbox not releasing some system-resource or kernel-resource. Following this theory, I found that as an interesting workaround, this bug does not occur as long as at least one qemu-kvm instance is running the moment a VirtualBox guest is started (the moment the "Press F12 to select Boot device" pops up in a new window). My guess is that this problem applies to VirtualBox-OSE as well, but I did not try that, yet. dmesg shows MSR write: 0x26e = 0x0 MSR write: 0x26f = 0x0 MSR write: 0x200 = 0xe0000000 MSR write: 0x201 = 0xffffffffe0000800 MSR write: 0x2ff = 0xc06 kvm: enabling virtualization on CPU1 failed kvm: enabling virtualization on CPU2 failed kvm: enabling virtualization on CPU3 failed (but I have seen a few CPU0 failed lines earlier) my rpm versions are kvm-kmp-default-78_2.6.27.7_9.1-6.4 kvm-78-6.4 VirtualBox-2.0.6_39765_openSUSE11-1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=460042 User novellbmw@lsmod.de added comment https://bugzilla.novell.com/show_bug.cgi?id=460042#c8 --- Comment #8 from Bernhard Wiedemann 2009-01-04 12:30:52 MST --- I did quite some extra testing with this KVM/VirtualBox interaction now.

Is the VirtualBox VM still running when you start the KVM VM? no, after the VirtualBox VM was running and stopped, KVM still failed with that "busy" error.

Could you please try to build a vanilla KVM version from kvm.sourceforge.net and see if modprob'ing that fails after you used VirtualBox? I used the kvm-78.tar.bz2 from the source RPM and interestingly kvm.ko and kvm-amd.ko did insmod just fine after using VirtualBox. What is even more interesting is that with this vanilla kvm module, qemu-kvm started working again which can easily be explained by the lacking check of the MSR_EFER_SVME_MASK bit (I looked at the source). However (on a sidenote), I also noticed a "kernel BUG at /home/bernhard/code/rpm/kvm/kvm-78/kernel/x86/kvm_main.c:1853!" in that vanilla kvm-78 when I tested its behaviour with both qemu-kvm and VirtualBox using SVM at the same time. This was folled by a complete panic on rmmod kvm

Finally, I added two printk lines to the opensuse-patched kvm-78/svm.c:313 ++ in the good case (before starting VirtualBox), dmesg has loaded kvm module (kvm-78) smp id=2 efer is d01 smp id=1 efer is d01 smp id=3 efer is d01 smp id=0 efer is d01 In the bad case (after starting and stopping VirtualBox) smp id=2 efer is 1d01 smp id=1 efer is 1d01 smp id=3 efer is 1d01 svm busy svm busy kvm: enabling virtualization on CPU1 failed kvm: enabling virtualization on CPU3 failed svm busy kvm: enabling virtualization on CPU2 failed Which clearly shows bit 12 set to 1 which means VirtualBox/vboxdrv is setting the EFER.SVME bit without need and not clearing it after use and not even on rmmod. Another interesting point is that when I activate AMD-V on my VirtualBox VM and start it and stop it, then the EFER.SVME bit is properly cleared, so that qemu-kvm just works again. To make sure that this issue has not been addressed by SUN in the meantime or was specific to the PUEL version, I also reproduced the very same behaviour with current VirtualBox-2.1.1-OSE-svn It properly releases SVME after using it for a VM, but it erroneously blocks SVME while and after _not_ using it in a VM without hardware-virtualisation. So it appears to me to be a bug in VirtualBox, while opensuse's KVM just does the right thing under these circumstances. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=460042 User novellbmw@lsmod.de added comment https://bugzilla.novell.com/show_bug.cgi?id=460042#c10 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|mkudlvasr@novell.com | --- Comment #10 from Bernhard Wiedemann 2009-01-17 08:05:37 MST --- I had filed this at http://www.virtualbox.org/ticket/3058 It is now fixed in SVN (I re-tested this today). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.