Red Hat Bugzilla – Bug 894345
PRD32 - [RFE] Spice arbitrary resolution
Last modified: 2016-02-10 15:21:06 EST
When resizing a spice client window, we adjust the Windows display resolution to do a best match, to avoid black-borders or scaling. The current driver supports only a limited set of resolutions. By adding arbitrary resolution, we can adjust guest display to fit exactly to the client window, for any size.
Components involved: spice-gtk - windows guest: win-qxl, spice-vdagent - linux guest: all components from bug 894350
For RHEL-6.4 and Windows guests running on RHEL-6.4 hosts, this feature should already be available. Code to support Windows guests is available in RHEVM-3.1 Code to support RHEL guests is available in RHEL-6.4 RHEL-6.4 qemu-kvm is needed on hosts for revision 4 of qxl device (this may also be done with previous RHEL hosts by changing the command line to specifically set qxl-vga revision to 4).
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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/RHSA-2013-0888.html