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.
Created attachment 1158647[details]
console_debug
previous discussion in bug 1129477 comment 48
Description of problem:
I have three monitors on my client. When I open Settings-> Displays they are numbered like this:
1 - Built-in
2 - NEC
3 - Acer.
I turned off Built-in display, so
2 - NEC
3 - Acer.
are active.
I map the monitors like this:
1) ~/.config/virt-viewer:
[rhel7.3]
monitor-mapping=1:3;2:2
Now I try to connect $remote-viewer spice://localhost:5900
then I get warning message:
remote-viewer-WARNING **: Initial monitor #3 for display #1 does not exist, skipping...
remote-viewer-WARNING **: display 0 should not be enabled, disabling
So the result is that guest display is only on 2 - NEC monitor.
Now some problems arise:
a) in this configuration mouse sometimes (~30% reproducibility) doesn't work in guest (cursor appears, but cannot interact) and I must leave full-screen mode and go back to enable it
b) sometimes (~35% reproducibility) is mouse cursor invisible over displayed VM desktop (is it at the background??)
c) sometimes (~15% reproducibility) blank screen appears on the monitor 3 - Acer with message: "Connected to graphic server" and no guest display appears. The debug report (--debug) from c) case is attached.
d) everything works as expected (~20% reproducibility)
I researched little bit more:
2) monitor-mapping=1:2;2:3
then I get warning message:
remote-viewer-WARNING **: Initial monitor #3 for display #2 does not exist, skipping...
and guest display is again on 2 - NEC monitor. (no problem with mouse or blank screen)
In the case of
3) monitor-mapping=1:1;2:2
both guest displays are spread over two client monitors, but if I get display IDs in guest (setting -> Displays), (2 - NEC monitor) is guest display 2 and (3 - Acer) is guest display 1.
For me it seems there is a mismatch in client monitor/guest display ID numbering. Would it be possible to reconcile the differences in numbering of gnome control panel with Gtk+ numbering? Or at least clarify the difference in virt-viewer documentation...
How reproducible:
as described above
Steps to Reproduce:
1. Create some VM
2. add monitor-mapping option to ~/.conf/virt-viewer/settings for particular VM
3. connect to VM :
$remote-viewer spice://$IP_VM:$PORT_VM -f
Actual results:
as described above
Expected results:
One guest display will be displayed on one client monitor (no blank screen). Mouse cursor should be visible and interact properly.
Additional info:
Hi, what is the version of virt-viewer and spice-gtk ?
a) not sure, would be nice to have more info - see also the bug 1286785
b) also reminds me the bug 1286785
c) it is bug 1323092
About the monitor mapping - we take info about it from gtk. Would be nice to know if Windows client and RHEL6 client has the same issue.
(In reply to Pavel Grunt from comment #2)
> Hi, what is the version of virt-viewer and spice-gtk ?
>
> a) not sure, would be nice to have more info - see also the bug 1286785
> b) also reminds me the bug 1286785
> c) it is bug 1323092
>
> About the monitor mapping - we take info about it from gtk. Would be nice to
> know if Windows client and RHEL6 client has the same issue.
Sorry I have forgotten to add versions:
virt-viewer-2.0-7.el7.x86_64
qemu-kvm-1.5.3-112.el7.x86_64
spice-gtk-0.31-2.el7.x86_64
Concerning c) - yes it seems it is a bug 1286785
I tried to reproduce this issue on RHEL 6.8 and Windows 8 clients ((closed) monitor of notebook) and rhel7.3 guest
With this output:
RHEL6.8 latest build:
----------------------
spice-server-0.12.4-13.el6.1.x86_64
spice-gtk-0.26-7.el6.x86_64
virt-viewer-2.0-14.el6.x86_64
qemu-kvm-0.12.1.2-2.491.el6.x86_64
monitor-mapping=1:3;2:2 - almost same behaviour as denoted for rhel7.3 client, but I was not able to reproduce non-visible cursor (issue b))
interesting part:
================
* in the case of monitor-mapping=1:2;2:1 both guest displays were on the same client monitor
* during my first attempts mouse pointer changed shape from arrow to 1x1cm black square (only over guest display). I was not able to reproduce this after approx. 5th connection to guest.
Windows 8
---------
virt-viewer v.2.0-129
monitor-mapping=1:3;2:2 - almost same behaviour as denoted for rhel7.3 client, but I was not able to reproduce non-visible cursor (issue b))
monitor-mapping=1:2;2:1 worked well
Radek, I would suggest to open separate bugs for the issues you found - if there are still present - or please clarify what is missing.
a) + b) - seems to be fixed per https://bugzilla.redhat.com/show_bug.cgi?id=1286785#c22
c) is bug 1323092 - fixed in spice-gtk-0.31-3.el7
yes all the issues seems to be fixed. I have tested it with rhel 7.3, rhel 6.8 and win7 guests (and rhel 7.3 client/host). If I supply incorrect monitor-mapping configuration, both displays are matched to client monitors and
(remote-viewer:19098): remote-viewer-WARNING **: Invalid monitor-mapping configuration: monitor #3 for display #1 does not exist
message appears.
Closing this.