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:
Windows guest ends up with black screen once spice vdagent resizes resolution to higher than 2560x1600 When arbitary resolution change is in use. Resizing back to lower resolution does not restore Guest screen.
The same feature in Linux guest does work and It's posible to resize guest resolution until limitation of buffer size.

Version-Release number of selected component (if applicable):
vdagent-win-0.1-12
qxl-win-unsigned-0.1-15

How reproducible:
Always

Steps to Reproduce:
1. Set resolution on Windows guest to 2560x1600
2. Resize spice client window to higher resolution.
  
Actual results:
Black screen only is displayed on the guest.

Expected results:
It should allow resizing until buffer size and or rollback once It's over.

Additional info:

There is an *unsigned* driver that contains the fix, setting Fixed-in and moving to MODIFIED.

The screen doesn't go black anymore, however when the resolution is changed by window resize and only one of the dimensions exceeds the limit, the resolution change fails completely. Would it be possible in such case to resize the guest to [min(desired_x, maximum_x), min(desired_y, maximum_y)] in 3.3 cycle?

(In reply to David Jaša from comment #4)
> ...
> Would it be possible in such case to
> resize the guest to [min(desired_x, maximum_x), min(desired_y, maximum_y)]
> in 3.3 cycle?

(In reply to David Jaša from comment #5)
> (In reply to David Jaša from comment #4)
> > ...
> > Would it be possible in such case to
> > resize the guest to [min(desired_x, maximum_x), min(desired_y, maximum_y)]
> > in 3.3 cycle?

I opened a separate bug for this: bug 1023423.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0053.html