Red Hat Bugzilla – Bug 864070
The combination of zoom & full screen with remote-viewer leaves big black bars on top & bottom when zoom is 66 and lower
Last modified: 2015-09-22 09:09 EDT
Description of problem:
When connecting to a a Win7 Guest with the latest qxl and virtio drivers using remote-viewer with the full screen option and the zoom option of 66 and below, the spice window appears full screen, but there are big black bars on the top and bottom of the screen.
This seems very strange since doing full-screen and the zoom option of 67 shows up full screen with no black bars on the top or bottom.
Version-Release number of selected component (if applicable):
Win 7 Guest:
Win 7 Client:
RHEL 6.3 Host:
Released version of 6.3 qemu-kvm & spice server
Steps to Reproduce:
1. remote-viewer --full-screen -zoom=<66 or lower> from mingw Win 7 64 client
full screen view of the guest with big black bars on the top and bottom of the screen.
full screen view of the guest
Marc-Andre, can you take a look?
Please try with a more recent mingw-virt-viewer build, mingw-virt-viewer-0.5.3-23.el6ev works for me.
Please try also with rhel6 virt-viewer.
It's probably not a driver bug. I am not sure that version of qxl driver has arbitrary resolution. I can't get the commit 100524f2478f3ee7a46774fe3841ce1449e3cfda from git://git.engineering.redhat.com/users/alevy/qxl.git
It should be there, since the next build qxl-win-unsigned-0.1-16 has it.
Tested this with the
mingw-virt-viewer-0.5.3-23.el6ev on Windows 7 with a Windows 7 & RHEL 6,4 guests, and this works.
Can you add this to the mingw-virt-viewer errata and then change it to ON_QA?
(In reply to comment #3)
> Tested this with the
> mingw-virt-viewer-0.5.3-23.el6ev on Windows 7 with a Windows 7 & RHEL 6,4
> guests, and this works.
> Can you add this to the mingw-virt-viewer errata and then change it to ON_QA?
Arbitrary resolution is part of the rebase for 3.2. And I am really not sure only mingw-virt-viewer fixed it, but rather an update of qxl or agent. I would rather just close that bug as current release.
*** This bug has been marked as a duplicate of bug 905898 ***