Bug 863082

Summary:	libvirtd guests fail to start with recent kernel
Product:	[Fedora] Fedora	Reporter:	Ian Dall <ian>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	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:		Environment:
Last Closed:	2012-10-04 13:54:11 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 Ian Dall 2012-10-04 12:05:25 UTC

Description of problem:
After a kernel upgrade, libvirtd/qemu/kvm virtual machines wont start

Version-Release number of selected component (if applicable):

kernel-3.5.4-2.fc17.x86_64

How reproducible:

Always

Steps to Reproduce:
1. virsh start <domain>
2. virsh list <domain>
3. virsh resume <domain>
  
Actual results:

After 2:

 Id    Name                           State
----------------------------------------------------
 1     <domain>                       paused

After 3, a log entry:

error : qemuMonitorJSONCheckError:331 : internal error unable to execute QEMU command 'cont': Resetting the Virtual Machine is required

If one then does "virsh reset <domain>" the reset doesn't throw any errors,
but the domain still can't be started.

Expected results:

 Id    Name                           State
----------------------------------------------------
 1     <domain.                        running


Additional info:

Reverting to kernel-3.5.2-3.fc17.x86_64 eliminates the problem

The libvirt version is libvirt-0.9.11.4-3.fc17.x86_64.

Comment 1 Josh Boyer 2012-10-04 13:06:29 UTC

This is likely a duplicate of 854983.  Does kernel-3.5.3 fail in a similar manner?

Comment 2 Ian Dall 2012-10-04 13:49:08 UTC

It does look like a duplicate of #854983. I guess my bugzilla-search-fu is not that great.

I don't have a kernel-3.5.3 and there isn't one in the repo anymore so it is not so easy to test.

Comment 3 Josh Boyer 2012-10-04 13:54:11 UTC

(In reply to comment #2)
> It does look like a duplicate of #854983. I guess my bugzilla-search-fu is
> not that great.

No problem.  We'll close this as a dup for now.

> I don't have a kernel-3.5.3 and there isn't one in the repo anymore so it is
> not so easy to test.

That's fine.  You could get it from koji if you really wanted, but we can just assume 3.5.3 is broken given bug 854983.

*** This bug has been marked as a duplicate of bug 854983 ***