Bug 1477191
| Summary: | Win10 VM does not keep number of attached displays after reconnection/migration | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Radek Duda <rduda> | ||||||||
| Component: | spice-vdagent-win | Assignee: | Default Assignee for SPICE Bugs <rh-spice-bugs> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | ybendito | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | --- | CC: | astepano, cfergeau, dblechte, emarcus, lsurette, rduda, rh-spice-bugs, spice-qe-bugs, srevivo, tpelka, uril, victortoso, ybendito | ||||||||
| Target Milestone: | rc | Keywords: | ZStream | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | vdagent-win-4.3-1 mingw-spice-vdagent-0.9.0-5 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: |
Windows 10 virtual machines did not report the correct number of connected displays following re-connection or migration. In this release, Windows 10 virtual machines correctly report the number of connected displays.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-06-20 14:46:55 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
VM qemu cmdline: usr/libexec/qemu-kvm -name guest=win10,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-win10/master-key.aes -machine pc-i440fx-rhel7.4.0,accel=kvm,usb=off,dump-guest-core=off -cpu Broadwell,+rtm,+hle,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 4dc7c629-448c-4dff-8891-6c86d59f745f -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-win10/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,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=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/home/rduda/Virtualky/Windows-10-20170725.0-x86_64.qcow2,format=qcow2,if=none,id=drive-ide0-0-0 -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/home/rduda/Virtualky/RHEV-toolsSetup_4.1_5.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -netdev tap,fd=26,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:70:d0:32,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=::,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device qxl,id=video1,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x8 -device qxl,id=video2,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x9 -device qxl,id=video3,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0xa -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 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on Created attachment 1307552 [details]
--spice-debug -debug log after reconnection
This applies not only for reconnection but also for migration (tested using using rhv 4.1.5-0.1.el7): Right after Windows 10 VM is migrated, number of attached displays is increased to the number of qxl devices of the VM. So several remote-viewer windows suddenly pop up. I don't see this getting into 4.2.0 - please re-target. This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. Any progress there? I reproduced this using rhv4.3 and rhel8 client/win10 guest(vdagent-win-4.1-5) again not a blocker for 4.3. Yuri, please, investigate and update. thanks, dnb Merged upstream https://gitlab.freedesktop.org/spice/win32/vd_agent/commit/93f3aee7b456e4845e6a4da77435484f188d4839 Created attachment 1542892 [details]
vdagent.exe (fix candidate)
Please check whether attached executable (comment #11) solves the problem (x64): from administrator command prompt: sc stop vdservice sc qc vdservice -> to see the path of executables copy attached vdagent.exe overriding existing restart It behaves all right with your new fix. Reproduced with current vdagent. Installed yours with a fix. I opened Win10 with 4 displays, closed one -> reconnected by remote-viewer -> only three displays were opened Repeated several times with various number of opened VM displays. 4.3.1 has been released, please re-target this bug as soon as possible. Is there an upstream release / downstream build including this fix? Hi Sandro,
> Is there an upstream release / downstream build including this fix?
Upstream I'm sure there isn't but I'll be preparing the releases Today and do one Tomorrow, I'll include win32/vd-agent too.
Downstream, It doesn't seem like it too? Unless I'm looking in the wrong place.
Moving back to POST, when build is done, added to errata, the fixed in version must be added.
Cheers,
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-2019:1555 |
Created attachment 1307549 [details] vdagent.log within reconnection Description of problem: After reconnection VM guest top up the number of attached displays to correlate number of qxl devices Version-Release number of selected component (if applicable): client: rhel7.4 tested: virt-viewer-5.0-7.el7.x86_64 spice-gtk3-0.33-6.el7.x86_64 spice-protocol-0.12.12-2.el7.noarch qemu-kvm-rhev-2.9.0-16.el7_4.3.x86_64 guest: Win10-64bit spice-qxl-wddm-dod-0.18-1 vdagent-win-4.1-3 How reproducible: always Steps to Reproduce: 1.Setup Win10 VM with multiple qxl devices and launch it (not in fullscreen) 2. connect to it with remote-viewer 3. reduce number of attached displays (remote-viewer menu-> View-> Displays) * notice that number of attached displays is accordingly reduced within Win10 guest (in 'Advanced display settings' dialog box) 4. reconnect to VM with remote-viewer Actual results: Number of attached displays is topped up to the number of guest's qxl devices Expected results: Number of attached displays stays the same before and after reconnection. Additional info: