Bug 234521 - kernel-xen should not include kvm modules
kernel-xen should not include kvm modules
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kernel-xen (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Xen Maintainance List
Brian Brock
:
Depends On:
Blocks: FC7Blocker
  Show dependency treegraph
 
Reported: 2007-03-29 15:59 EDT by Will Woods
Modified: 2007-11-30 17:12 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-30 10:43:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Will Woods 2007-03-29 15:59:39 EDT
The current package (kernel-xen-2.6.20-2925.5.fc7) contains the kvm modules.
When these are loaded (by libvirt-qemud, presumably) the kernel crashes. Hard.
The traceback shows kvm_intel all over the place.

Moving the /lib/modules/$(uname -r)/kernel/drivers/kvm directory allows the
system to boot and run normally.

As I understand it, these two things are fundamentally incompatible, and
kernel-xen should just have its config changed to not build the kvm modules.
Comment 1 Daniel Berrange 2007-03-29 16:18:06 EDT
I dunno what's causing them to be loaded, but its not  libvirt_qemud - we merely
check for existance of /dev/kvm - we never try to actually create it / load
modules to create it. You're right that we need to kill the kvm modules from the
kernel-xen though - they simply won't co-exist with Xen because the Xen HV has
taken ownership of the VMX / SVM  capabilities.
Comment 2 Jarod Wilson 2007-03-30 10:43:23 EDT
CONFIG_KVM, CONFIG_KVM_INTEL and CONFIG_KVM_AMD have all been disabled for the
next kernel build.

Note You need to log in before you can comment on or make changes to this bug.