Mailinglist Archive: opensuse-bugs (13048 mails)

< Previous Next >
[Bug 460042] [Virtualization:KVM] kernel: kvm: enabling virtualization on CPU1 failed
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 3 Jan 2009 23:31:02 -0700 (MST)
  • Message-id: <20090104063102.AC442245390@xxxxxxxxxxxxxxxxxxxxxx>

User novellbmw@xxxxxxxx added comment

Bernhard Wiedemann <novellbmw@xxxxxxxx> changed:

What |Removed |Added
Resolution|INVALID |

--- Comment #6 from Bernhard Wiedemann <novellbmw@xxxxxxxx> 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 #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
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

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >