Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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...
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).
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
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