Bug 234521

Summary:	kernel-xen should not include kvm modules
Product:	[Fedora] Fedora	Reporter:	Will Woods <wwoods>
Component:	kernel-xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED RAWHIDE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	bstein, jarod, xen-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-03-30 14:43:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	150226

Description Will Woods 2007-03-29 19:59:39 UTC

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 Berrangé 2007-03-29 20:18:06 UTC

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 14:43:23 UTC

CONFIG_KVM, CONFIG_KVM_INTEL and CONFIG_KVM_AMD have all been disabled for the
next kernel build.