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.
Bug 1539735 - Only one feasible display after remote-viewer connection to fully established VM
Summary: Only one feasible display after remote-viewer connection to fully established VM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-29 14:23 UTC by Radek Duda
Modified: 2018-04-10 13:55 UTC (History)
7 users (show)

Fixed In Version: spice-server-0.14.0-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 13:55:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
spice-debug log after connection to fully established VM (41.98 KB, text/plain)
2018-01-29 14:23 UTC, Radek Duda 		no flags Details
spice-debug log: connection right after boot (all displays available then) (1.28 MB, text/plain)
2018-01-29 14:24 UTC, Radek Duda 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0802 0 None None None 2018-04-10 13:55:42 UTC

Description Radek Duda 2018-01-29 14:23:03 UTC 
Created attachment 1387826 [details]
spice-debug log after connection to fully established VM

Description of problem:
No additional display could be attached after remote-viewer connects to fully established VM.

Version-Release number of selected component (if applicable):
guest (rhel7.5):
spice-server-0.14.0-2.el7.x86_64
spice-vdagent-0.14.0-15.el7.x86_64

host:
qemu-kvm-rhev-2.9.0-16.el7_4.14.x86_64

client (rhel7.5):
virt-viewer-5.0-10.el7.x86_64
spice-gtk3-0.34-3.el7.x86_64

rhv-4.2:
ovirt-engine-4.2.1.3-0.1.el7.noarch

How reproducible:
always

Steps to Reproduce:
1.Create rhel VM with more heads (e.g. 4) in rhv:
..
    <video>
      <model type="qxl" vram="131072" heads="4" ram="262144" vgamem="65536"/>
      <address bus="0x00" domain="0x0000" function="0x0" slot="0x02" type="pci"/>
    </video>
..
2. launch it
3. when the GNOME desktop environment is established, connect to it with remote-viewer 
4. got to remote-viewer's menu (View -> Displays)

Actual results:
only one Display is available to attach.


Expected results:
Four displays should be available.

Additional info:
* If remote-viewer is connected to VM right after boot (before GNOME desktop is loaded), all 4 displays are available in the menu.
* I cannot reproduce this bug with libvirt VM. only with VM running in RHV.



full qemu-kvm cmdline:
/usr/libexec/qemu-kvm -name guest=rhel7-64,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-rhel7-64/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off -cpu SandyBridge -m size=4096000k,slots=16,maxmem=8192000k -realtime mlock=off -smp 4,maxcpus=16,sockets=16,cores=1,threads=1 -numa node,nodeid=0,cpus=0-3,mem=4000 -uuid e9914a3a-000c-424c-b4fd-c8f852d619d1 -smbios type=1,manufacturer=oVirt,product=RHEV Hypervisor,version=7.4-18.el7,serial=4C4C4544-0054-4710-8059-B1C04F37354A,uuid=e9914a3a-000c-424c-b4fd-c8f852d619d1 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-rhel7-64/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2018-01-29T14:05:46,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x8.0x7 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x8.0x2 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x8.0x1 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x8 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x9 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -device usb-ccid,id=ccid0,bus=usb.0,port=1 -drive if=none,id=drive-ide0-1-0,readonly=on,werror=report,rerror=report,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/5325e826-d91c-4c95-be07-51011bf28943/images/395df216-b534-4175-9514-f5fcda78c60f/7d5c5d5e-aabc-4015-93b2-61b8dd9567cc,format=qcow2,if=none,id=drive-virtio-disk0,serial=395df216-b534-4175-9514-f5fcda78c60f,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:04,bus=pci.0,addr=0x3 -chardev spicevmc,id=charsmartcard0,name=smartcard -device ccid-card-passthru,chardev=charsmartcard0,id=smartcard0,bus=ccid0.0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/e9914a3a-000c-424c-b4fd-c8f852d619d1.ovirt-guest-agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=ovirt-guest-agent.0 -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/e9914a3a-000c-424c-b4fd-c8f852d619d1.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice tls-port=5900,addr=10.37.175.76,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,seamless-migration=on -device qxl-vga,id=video0,ram_size=268435456,vram_size=134217728,vram64_size_mb=0,vgamem_mb=64,max_outputs=4,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -chardev spicevmc,id=charredir2,name=usbredir -device usb-redir,chardev=charredir2,id=redir2,bus=usb.0,port=4 -chardev spicevmc,id=charredir3,name=usbredir -device usb-redir,chardev=charredir3,id=redir3,bus=usb.0,port=5 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0xa -msg timestamp=on
Comment 2 Radek Duda 2018-01-29 14:24:32 UTC 
Created attachment 1387827 [details]
spice-debug log: connection right after boot (all displays available then)
Comment 4 Victor Toso 2018-02-01 14:28:01 UTC 
Regression, yes. Reproducible with rhev 4.2 too.
Comment 5 Victor Toso 2018-02-01 15:45:40 UTC 
logout and login works as workaround here.
Comment 6 Radek Duda 2018-02-01 16:27:02 UTC 
(In reply to Victor Toso from comment #5)
> logout and login works as workaround here.

We then agreed that resize of remote-viewer's window is workaround - not relog
Comment 7 David Blechter 2018-02-01 17:49:41 UTC 
(In reply to Radek Duda from comment #6)
> (In reply to Victor Toso from comment #5)
> > logout and login works as workaround here.
> 
> We then agreed that resize of remote-viewer's window is workaround - not
> relog

with workaround we should move to 7.6, and 7.5.z with high severity. Not enough time for 7.5
Comment 9 Victor Toso 2018-02-06 15:32:24 UTC 
This is host/guest side. I can see by enabling the debug from spice-server that, sometimes, we receive max:1 instead of max:4

Expected:

(process:979): Spice-DEBUG: display-channel.c:181:monitors_config_debug: monitors config count:1 max:4

Bug:

(process:1373): Spice-DEBUG: display-channel.c:181:monitors_config_debug: monitors config count:1 max:1
Comment 10 Radek Duda 2018-02-08 11:28:02 UTC 
Sorry I did not mention spice-server used in host:
spice-server-0.12.8-2.el7.1.x86_64
Comment 11 Victor Toso 2018-02-08 11:53:22 UTC 
I can confirm that in rhev4.2, with spice-server-0.12.8-2.el7.1.x86_64 we have the issue but no problem with spice-server-0.14.0-2.el7.x86_64

Only an issue for RHV 4.2

As the bug has low impact with easy workaround, I suggest to move it to RHV 4.3 as We should be upgrade spice server to the same as RHEL 7.5 or RHEL 7.6.

The bug itself seems to happen because spice-server clears the monitor config (with correct values) when user logins. The problem does not happen after the code refactoring done between 0.12 and 0.14.
Comment 12 Victor Toso 2018-02-08 12:11:09 UTC 
RHV takes latest packages available on RHEL-7 so it should be fixed by RHV 4.3
Comment 13 Victor Toso 2018-02-08 13:05:46 UTC 
Moving it to POST, this is fixed by RHEL 7.5 and can be added to errata.
Comment 15 Victor Toso 2018-02-13 06:33:46 UTC 
Moving to MODIFIED so we can add to errata 30036
Comment 16 Victor Toso 2018-02-13 06:35:25 UTC 
Sorry, my mistake. Already in errata 30631
Comment 20 errata-xmlrpc 2018-04-10 13:55:36 UTC 
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://access.redhat.com/errata/RHBA-2018:0802
Note You need to log in before you can comment on or make changes to this bug.