Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Previously, when opening a connection to a Windows guest on a four monitors host, only one monitor gets enabled. With this update, the spice agent copes with monitor configuration refresh during reconfiguration, and all monitors will get enabled.
Description of problem:
remote-viewer only show one display if connect windows 7 guest on a 4 monitors machine, if try 2 or 3 times, it works.
Version-Release number of selected component (if applicable):
virt-viewer-0.6.0-7.el6.x86_64
spice-server-0.12.4-9.el6.x86_64
spice-gtk-python-0.22-4.el6.x86_64
spice-vdagent-0.14.0-3.el6_5.x86_64
spice-gtk-0.22-4.el6.x86_64
spice-xpi-2.7-24.el6.x86_64
spice-glib-0.22-4.el6.x86_64
virtio-win-1.6.8-4.el6
How reproducible:
100%
Steps to Reproduce:
1. Install a win7 guest on a 4 monitors machine, install spice agent and qxl dirver in it.
2. configure it with only one display first
# virt-viewer $vm
make sure only one display comes out
3. close virt-viewer, use remote-viewer connect the guest
# remote-viewer spice://$ip/$port --full-screen --debug
Actual results:
Stpe3, only two displays comes out with fullscreen,
but seems 4 displays are ok form log.
# cat $log
(remote-viewer:17024): remote-viewer-DEBUG: Insert window 0 0x1a70840
(remote-viewer:17024): remote-viewer-DEBUG: Insert window 1 0x1a70e40
(remote-viewer:17024): remote-viewer-DEBUG: Insert window 2 0x1ab9e10
(remote-viewer:17024): remote-viewer-DEBUG: Insert window 3 0x1ae1240
(remote-viewer:17024): remote-viewer-DEBUG: fullscreen display 0: 1
(remote-viewer:17024): remote-viewer-DEBUG: fullscreen display 1: 1
(remote-viewer:17024): remote-viewer-DEBUG: fullscreen display 3: 1
(remote-viewer:17024): remote-viewer-DEBUG: fullscreen display 2: 1
...
when I connect the guest second time, 3 displays comes out
when I connect it third time, 4 displays comes out.
Expected results:
4 displays should come out in fullscreen mode when I connect it first time
Additional info:
Comment 3Marc-Andre Lureau
2014-06-19 11:07:20 UTC
This is unlikely a client bug, auto-conf is correct:
(remote-viewer:17024): remote-viewer-DEBUG: Performing full screen auto-conf, 4 host monitors
(remote-viewer:17024): remote-viewer-DEBUG: Set SPICE display 0 to (0,0)-(1280x1024)
(remote-viewer:17024): remote-viewer-DEBUG: Set SPICE display 1 to (1280,0)-(1280x1024)
(remote-viewer:17024): remote-viewer-DEBUG: Set SPICE display 2 to (2560,0)-(1680x1050)
(remote-viewer:17024): remote-viewer-DEBUG: Set SPICE display 3 to (4240,0)-(1280x1024)
(remote-viewer:17024): GSpice-DEBUG: channel-main.c:1176 main-1:0: monitor config: #0 1280x1024+0+0 @ 32 bpp
(remote-viewer:17024): GSpice-DEBUG: channel-main.c:1176 main-1:0: monitor config: #1 1280x1024+1280+0 @ 32 bpp
(remote-viewer:17024): GSpice-DEBUG: channel-main.c:1176 main-1:0: monitor config: #2 1680x1050+2560+0 @ 32 bpp
(remote-viewer:17024): GSpice-DEBUG: channel-main.c:1176 main-1:0: monitor config: #3 1280x1024+4240+0 @ 32 bpp
What are the windows driver & vdagent version?
Please get the full windows vdagent debug log
Comment 4Marc-Andre Lureau
2014-06-19 13:14:44 UTC
I can reproduce, using upstream spice-guest-tools-0.74.exe on rhevm 3.4
However, I couldn't reproduce on f20 with qxl 6.1.0.10018 and spice agent 0.7.2.7-1b0e
Comment 5Marc-Andre Lureau
2014-06-19 13:18:52 UTC
(In reply to Marc-Andre Lureau from comment #4)
> I can reproduce, using upstream spice-guest-tools-0.74.exe on rhevm 3.4
>
> However, I couldn't reproduce on f20 with qxl 6.1.0.10018 and spice agent
> 0.7.2.7-1b0e
actually, result is random, looks like something racy, ok moving component
CongDong, no need for logs, it can be reproduced.
thanks
Comment 6Marc-Andre Lureau
2014-06-19 13:48:42 UTC
Hi Marian,
If this bug requires doc text for errata release, could you provide draft text in the following format:
Cause:
Consequence:
Fix:
Result:
The documentation team will review, edit, and approve the text.
If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
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.
https://rhn.redhat.com/errata/RHBA-2015-0204.html