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:
Use virt-viewer to connect a running rhel guest, then open "Display preferences", the resolution will change to other.

Version-Release number of selected component (if applicable):
libvirt-0.10.2-21.el6.x86_64
virt-viewer-0.5.6-6.el6.x86_64
qemu-kvm-0.12.1.2-2.382.el6.x86_64
spice-vdagent-0.14.0-1.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Create a rhel guest with spice+qxl+spicevmc.
2.# virt-viewer $NAME
3.Open "Display preferences" in guest :   System -> Preferences -> Display preferences , and just open it is ok, don't try to change the resolution manually.
4.Repeat step3 sevral times.

Actual results:
Step4, the resolution will change everytime when do step3.

Expected results:
The resolution should not change, except change it manually.

Additional info:

Created attachment 782653 [details]
virt-viewer debug log

Created attachment 782654 [details]
xorg log

the client get a resolution change from the guest, most likely a guest driver issue (probably randr related)

I can't reproduce. Is it still reproducible on your side? thanks

(In reply to Marc-Andre Lureau from comment #6)
> I can't reproduce. Is it still reproducible on your side? thanks

I cannot reproduce this anymore.

thanks