Bug 911640

Summary:	KVM module denies access after installation until reboot or reload
Product:	[Fedora] Fedora	Reporter:	Martin Kletzander <mkletzan>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	911644 (view as bug list)		Environment:
Last Closed:	2013-07-24 18:54:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Kletzander 2013-02-15 14:17:29 UTC

Description of problem:
After fresh installation, qemu, libvirt and others are unable to access /dev/kvm even though the permissions are correct, even when you change them to anything else and even when trying as root.  This problem goes away after reboot or after running 'rmmod kvm; modprobe kvm'.  Apparently, this happens only on some hardware, but on such hardware it should be 100% reproducible.

This has appeared in bug 877436, bug 911346 and once it happened on a machine (X230) in our office.

Version-Release number of selected component (if applicable):
Released F18 x86_64 DVD and others (see bugs mentioned above).

How reproducible:
HW-dependant (probably)

Steps to Reproduce:
1. Perform a fresh install of the system
2. Try open()-ing /dev/kvm or running a KVM virtual machine or check 'virsh capabilities' for '<capabilities><guest><os_type>hvm</os_type>'
3. Reboot or reload the kvm module
4. Repeat step 2 and check the difference
  
Actual results:
First time you'll get permission denied and second time it will work.

Expected results:
It works first time as well.

Comment 1 Josh Boyer 2013-07-03 16:50:09 UTC

Are you still seeing this with the 3.9 or 3.10 kernels?  If so, can you please attach the output of dmesg?

Comment 2 Josh Boyer 2013-07-24 18:54:57 UTC

This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.