Bug 1499519

Summary:	KVM Windows guest random freeze with 100% cpu
Product:	[Fedora] Fedora	Reporter:	Kristian Feldsam <admin>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	26	CC:	admin, airlied, bskeggs, eparis, esandeen, hdegoede, ichavero, itamar, jarodwilson, jforbes, jglisse, jonathan, josef, jwboyer, kernel-maint, labbott, linville, mchehab, mjg59, nhorman, quintela, steved
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-16 17:15:37 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 Kristian Feldsam 2017-10-08 10:51:20 UTC

Description of problem:
After upgrading to kernel 4.13.4-200.fc26.x86_64 Windows 7 guest freeze randomly, most items short time after boot.

Version-Release number of selected component (if applicable):
4.13.4-200.fc26.x86_64

How reproducible:
with latest virtio drivers look like that first VM on host is running fine until second one is started (just hypotese). Also after drivers upgrade it takes more tim eto freeze or it freeze less often

Steps to Reproduce:
1. Start Windows 7 VM. XML dump https://pastebin.com/9NhX0dVK

Actual results:
VM freeze with 100%

Expected results:
VM does not freeze

Additional info:

Comment 1 Kristian Feldsam 2017-10-08 10:53:54 UTC

*most times short time after boot

Comment 2 Kristian Feldsam 2017-10-26 20:57:51 UTC

Update: After VM hard reset, it still consume 100% cpu and can't boot, hangs on "Booting from Hard Disk..."

Only thing which work is destroy and create VM....it freeze after some time again.

Now tested with latest fc26 kernel 4.13.9-200

Comment 3 Laura Abbott 2018-02-28 03:52:53 UTC

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Comment 4 Kristian Feldsam 2018-04-14 10:33:08 UTC

Hello, looks like working now. Tested for 13days on 4.15.12-201.fc26.x86_64.

Comment 5 Laura Abbott 2018-04-16 17:15:37 UTC

Thanks for letting us know.