Red Hat Bugzilla – Bug 863488
Windows guest ends up with black screen after resizing spice client window over 2560x1600 resolution
Last modified: 2015-09-22 09:10 EDT
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):
Steps to Reproduce:
1. Set resolution on Windows guest to 2560x1600
2. Resize spice client window to higher resolution.
Black screen only is displayed on the guest.
It should allow resizing until buffer size and or rollback once It's over.
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.