Bug 886125

Summary:	guest screen freezes after resolution change on 6.4 qemu with -M <= rhel6.3.0
Product:	Red Hat Enterprise Linux 8	Reporter:	David Jaša <djasa>
Component:	spice-qxl-xddm	Assignee:	Alon Levy <alevy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	---	CC:	acathrow, cfergeau, dblechte, kraxel, pvine
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-29 10:48:50 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:
Bug Depends On:
Bug Blocks:	1019461

Description David Jaša 2012-12-11 15:10:06 UTC

Description of problem:


Version-Release number of selected component (if applicable):
guest:
qxl-win-0.1-17 (observed at least from -15 but not pinpointed by then)
windows version doesn't matter

host:
qemu-kvm-0.12.1.2-2.340.el6.x86_64
seabios-0.6.1.2-25.el6.x86_64
vgabios-0.6b-3.7.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. install windows VM; make sure you run qemu with -M <= rhel6.3.0 (tested with "-M rhel6.3.0" and "-M rhel6.2.0"
2. install qxl driver in the VM; reboot
3. change resolution
  
Actual results:
guest gets unresponsive, screen is stuck. When you reconnect to the VM, screen is black. Guest never unfreezes again.
After you kill the VM and power it up again, guest comes up with the new resolution

Expected results:
guest changes resolution and works normally again

Additional info:
*** This bug should be resolved before RHEL 6.4 release so it should make it to 3.1.z stream ***

Few seconds after the guest spice display freezes, you can RDP to it, but the guest freezes at login screen anyway.

"-M rhel6.4.0" sets qxl revision to 4, "-M rhel6.0.0" to "-M rhel6.3.0" sets qxl revision to 3.

Comment 1 David Jaša 2012-12-11 15:17:01 UTC

One more information: VMs on RHEL 6.3 hosts are not affected so RHEV-M 3.1 as of now is not affected - it will be when RHEL 6.4 hits repos and hosts will be updated to it...

Comment 2 Alon Levy 2012-12-11 15:56:43 UTC

Just a note: the fact that "-M rhel6.0.0" sets the revision to 3 is a rhel specific bug, fixed in bug 733302 scratch build http://brewweb.devel.redhat.com/brew/taskinfo?taskID=5176642

But that's probably not related - just saying it would help to provide the qxl revision in addition to the machine type because of bug 733302 causing them to not match like we assumed (6.2.0 is not 2, but actually 3, like you noticed).

Comment 3 David Jaša 2012-12-12 09:53:24 UTC

Given that bug 864982 depends on qemu machine version in the same way, this could turn out be actually qemu bug as well...

Comment 4 Alon Levy 2013-07-29 08:36:43 UTC

Sorry for the long time without a resolution. However now I tried to reproduce but couldn't, I tried both -M RHEL-6.2.0 and RHEL-6.3.0, once I thought I had it but cannot reproduce it. I'm using qemu-kvm-0.12.1.2-2.378.el6 plus some unrelated patches from git.

If you cannot reproduce this (sorry again for the long delay) I'll close it as worksforme.

Alon

Comment 5 Alon Levy 2013-07-29 10:48:50 UTC

Tested with -Mrhel6.4.0 as well (comment 4 has the wrong machine strings, they should be rhel6.3.0 and rhel6.2.0), could not reproduce, closing as currentrelease per talk with David Jasa who reproduced this originally.

Alon