Spice Proxy Issues Between Cluster Nodes

TruePath_Tech

New Member
Sep 12, 2018
5
1
3
39
We're having an issue with spice proxy after we upgraded our cluster from PVE 5.1 to 5.2.

Prior to the upgrade, we were able to log into the webUI of any node in the cluster and access a VM running on any other node in the cluster with remote-viewer (spice). After the update, we are now only able to access VMs on the Proxmox host we are logged into. If we try to connect to a VM hosted on another node in the cluster, it says "Unable to connect to the graphics server <filename>".

Output of "pveversion -v"
Code:
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-8 (running version: 5.2-8/fdf39912)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-27
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
openvswitch-switch: 2.7.0-3
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-30
pve-container: 2.0-26
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-33
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Everything else in the cluster is working as expected. I'm at a bit of a loss on what to try next for this issue. Any assistance is appreciated.

Thanks!
 
Additional diagnostic info:

spice proxy debug mode on the logged in WebUI host when connection fails
Code:
1902: ACCEPT FH10 CONN1
REMOTE CONNECT 110, <Remote host IP redacted>, pvespiceproxy:5b9985a8:110:<remote hostname redacted>::ca43df6b7a9d6027b82c419b57b608c77cb83843:61000
1902: CONNECTed to '<remote IP redacted>:3128'
close connection AnyEvent::Handle=HASH(0x5556b4096fb0)
1902: CLOSE FH10 CONN0

spice proxy debug mode on remote proxmox host
Code:
9751: ACCEPT FH10 CONN1
9751: CONNECT 110, <remote IP redacted>, 61000
9751: CONNECTed to 'localhost:61000'
close connection AnyEvent::Handle=HASH(0x558cd9455770)
9751: CLOSE FH10 CONN0

After we saw the SSL errors in the log, we decided to rebuild all the certs. We moved:
  • /etc/pve/pve-root-ca.pem
  • /etc/pve/priv/pve-root-ca.key
  • /etc/pve/nodes/<all nodes>/pve-ssl.pem
  • /etc/pve/nodes/<all nodes>/pve-ssl.key
Once the certs were moved, we regenerated them on all nodes with pvecm updatecerts -f and rebooted all the hosts.
 
syslog entry on the logged in WebUI host when connection fails
NOTE: There is no syslog entry on the VMs host when a connection fails
Code:
Sep 12 16:27:12 <hostname redacted> spiceproxy[13756]: problem with client <IP redacted>; Connection reset by peer
 
I'm trying to post the local remote-viewer logs as well but they keep telling me that it's an outside link... Here is the relevant line I believe.

remote-viewer -v --spice-debug
NOTE: This is virt-viewer V7 but we have other users testing with virt-viewer V6 as well
Code:
(remote-viewer:23248): GSpice-WARNING **: 16:36:02.439: main-1:0: SSL_connect: error:00000001:lib(0):func(0):reason(1)
 
Is it possible to disable certificate pinning for the spice proxy? If not disable, then at least force an update? I'd like to test it to see if perhaps that's the issue. Thanks!
 
  • Like
Reactions: ekin06
Thank god we are not alone! ;) We do have the very same problem like TruePath_Tech describes.

We have eight nodes in a Proxmox cluster while four are in a Ceph cluster. The last three do not host anything, they are providing ISCSI-LUNs for node 1. The webUI is reachable via internal domain "proxmox.domain.xyz", which randomly selects one of the nodes (lets call them pve01-pve08) as login-node. You can login and connect to your appropriate VM via spice. The spice clients can be on Win10, Win7 or Linux. All worked like a charm several months, but things got messed up when we did the upgrade from kernel 4.15.17-3-pve to 4.15.18-3-pve (now its 4.15.18-4-pve).

You open spice console (node or vms doesnt matter) and get the error message:
Unable to connect to the graphic server

If you are logged to node1, you can open spice for all VMs hosted on this node.
If you are logged to node1 you can NOT open spice for all VMs hosted on other nodes.
Under special circumstances the spice-console did no open for any VM or node (have not yet reproduced).

If you download the viewer file and open it right after with --spice-debug you get:
Code:
C:\Program Files\VirtViewer v6.0-256\bin>remote-viewer.exe --spice-debug c:\Users\###\Downloads\YnNzsq0m.vv

C:\Program Files\VirtViewer v6.0-256\bin>
(remote-viewer.exe:18632): Gtk-WARNING **: Could not find signal handler 'virt_viewer_window_menu_change_cd_activate'.  Did you compile with -rdynamic?
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:285 New session (compiled from package spice-gtk 0.33)
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:289 Supported channels: main, display, inputs, cursor, playback, record, usbredir
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usbdk_api.c:62 UsbDk driver is installed.
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usbdk_api.c:86 Loading UsbDk API DLL
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usb-device-manager.c:528 auto-connect filter set to 0x03,-1,-1,-1,0|-1,-1,-1,-1,1
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usb-device-manager.c:2196 Auto-connect disabled, no hider setup needed
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0bf8:1028 (0000000004500020)
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 093a:2510 (0000000004500B20)
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 096e:0006 (0000000004500C20)
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0951:16b3 (00000000045009C0)
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0bda:0184 (0000000004500E20)
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:1736 no migration in progress
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:137 main-1:0: spice_channel_constructed
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:2239 main-1:0: new main channel, switching
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:2610 main-1:0: Open coroutine starting 00000000042ABFD0
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:2451 main-1:0: Started background coroutine 00000000042ABE68
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:2173 Missing port value, not attempting unencrypted connection.
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:2477 main-1:0: trying with TLS port
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:2185 main-1:0: Using TLS, port 61000
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:2133 (with proxy http://pve02.domain.xyz:3128)
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:2057 proxy lookup ready
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:2040 main-1:0: connecting 000000000899FE10...
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-session.c:2024 main-1:0: connect ready
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:2379 main-1:0: Load CA, file: (NULL), data: 00000000043074A0

(remote-viewer.exe:18632): Spice-WARNING **: ../../../spice-common/common/ssl_verify.c:437:openssl_verify: Error in certificate chain verification: self signed certificate in certificate chain (num=19:depth1:/CN=Proxmox Virtual Environment/OU=30119197-e9ca-42b7-bbc1-327ea6ab5951/O=PVE Cluster Manager CA)
(remote-viewer.exe:18632): Spice-DEBUG: ../../../spice-common/common/ssl_verify.c:447:openssl_verify: server certificate not being signed by the provided CA

(remote-viewer.exe:18632): GSpice-WARNING **: main-1:0: SSL_connect: error:00000001:lib(0):func(0):reason(1)
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:2587 main-1:0: Coroutine exit main-1:0
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:2780 main-1:0: reset
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/channel-main.c:1537 agent connected: no
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:2722 main-1:0: channel reset
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/bio-gio.c:78 bio gsocket destroy
(remote-viewer.exe:18632): GSpice-DEBUG: ../../src/spice-channel.c:2328 main-1:0: Delayed unref channel 00000000042ABFD0

We use virt-viewer v6, but tried v7 for this scenario too.

I just notices that "Error in certificate chain verification: self signed certificate in certificate chain (num=19:depth1:/CN=Proxmox Virtual Environment/OU=30119197-e9ca-42b7-bbc1-327ea6ab5951/O=PVE Cluster Manager CA)" is not the same OU what the browser says?

Code:
CN = Proxmox Virtual Environment, OU = 6062ec9d-a447-46f9-923c-4017df4f8c19, O = PVE Cluster Manager CA
-> the actual one and I can see with "openssl x509 -in /etc/pve/pve-root-ca.pem -text -noout" that this Proxmox Root CA on every single node is the same.

I restarted services, then nodes and since all did not help I recreated certificates from the beginning (pvecm updatecerts -f + node-restart), cleared browser cache, changed browser, tried different clients with no luck.

BEFORE UPGRADE: To be a trusted host within the browser, I did create a self-signed cert with the Proxmox Root CA via openssl, which is valid for every single node. This worked for us since now. I used the following commands:
Code:
#!/bin/bash

openssl req -newkey rsa:2048 -keyout proxmox.domain.xyz.key -out proxmox.domain.xyz.csr -sha256 -nodes
openssl x509 -req -CA pve-root-ca.pem -CAkey pve-root-ca.key -in proxmox.domain.xyz.csr -out proxmox.domain.xyz.crt -days 10000 -extfile proxmox-nodes.ext -sha256 -set_serial 0x1114

cat proxmox.domain.xyz.crt > pve-ssl.pem
cat pve-root-ca.pem >> pve-ssl.pem

cat proxmox.domain.xyz.key > pve-ssl.key

Code:
 extendedKeyUsage = serverAuth
 subjectAltName = @alt_names
[ alt_names ]
 DNS.1 = proxmox.domain.xyz
 DNS.2 = pve01.domain.xyz
 DNS.3 = pve02.domain.xyz
 DNS.4 = pve03.domain.xyz
 DNS.5 = pve04.domain.xyz
 DNS.6 = pve05.domain.xyz
 DNS.7 = pve06.domain.xyz
 DNS.8 = pve07.domain.xyz
 DNS.9 = pve08.domain.xyz

Looks like remote-viewer / spice is catching a wrong cert?



Code:
# Debian Repo
deb http://ftp.de.debian.org/debian stretch main contrib

# Debian security updates
deb http://security.debian.org stretch/updates main contrib

# PVE No-subscription Repo
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

#RAID Software Repo
deb http://hwraid.le-vert.net/debian stretch main

All nodes should be at the same patchlevel now.

Code:
~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-3-pve: 4.15.18-22
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-28
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-34
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Code:
~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-2-pve: 4.13.13-33
ceph: 12.2.8-pve1
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-28
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-34
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Code:
~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-2-pve: 4.13.13-33
ceph: 12.2.8-pve1
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-28
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-34
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Code:
pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-2-pve: 4.13.13-33
ceph: 12.2.8-pve1
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-28
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-34
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Code:
~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-2-pve: 4.13.13-33
ceph: 12.2.8-pve1
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-28
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-34
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Code:
~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-3-pve: 4.15.18-22
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-28
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-34
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Code:
~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-3-pve: 4.15.18-22
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-28
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-34
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Code:
~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-7
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-3-pve: 4.15.18-22
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-28
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-34
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9



Code:
Start-Date: 2018-08-30  12:34:39
Commandline: apt-get dist-upgrade
Install: libtcmalloc-minimal4:amd64 (2.5-2.2, automatic), ceph-fuse:amd64 (10.2.5-7.2, automatic), libgoogle-perftools4:amd64 (2.5-2.2, automatic), pve-kernel-4.15.18-3-pve:amd64 (4.15.18-22, automatic), libunwind8:amd64 (1.1-4.1, automatic)
Upgrade: fuse:amd64 (2.9.7-1, 2.9.7-1+deb9u1), libcups2:amd64 (2.2.1-8+deb9u1, 2.2.1-8+deb9u2), linux-libc-dev:amd64 (4.9.88-1+deb9u1, 4.9.110-3+deb9u4), libldap-2.4-2:amd64 (2.4.44+dfsg-5+deb9u1, 2.4.44+dfsg-5+deb9u2), libpve-storage-perl:amd64 (5.0-23, 5.0-25), libxapian30:amd64 (1.4.3-2, 1.4.3-2+deb9u1), libwbclient0:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), libsystemd0:amd64 (232-25+deb9u2, 232-25+deb9u4), pve-firmware:amd64 (2.0-4, 2.0-5), pve-qemu-kvm:amd64 (2.11.1-5, 2.11.2-1), pve-docs:amd64 (5.2-4, 5.2-8), openssh-sftp-server:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), pve-firewall:amd64 (3.0-12, 3.0-14), udev:amd64 (232-25+deb9u2, 232-25+deb9u4), pve-container:amd64 (2.0-23, 2.0-26), libmagic1:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), pve-cluster:amd64 (5.0-27, 5.0-30), libudev1:amd64 (232-25+deb9u2, 232-25+deb9u4), samba-libs:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), dpkg:amd64 (1.18.24, 1.18.25), libmagic-mgc:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), pve-manager:amd64 (5.2-2, 5.2-8), reportbug:amd64 (7.1.7+deb9u1, 7.1.7+deb9u2), pve-kernel-4.15.17-3-pve:amd64 (4.15.17-12, 4.15.17-14), libfuse2:amd64 (2.9.7-1, 2.9.7-1+deb9u1), ssh:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), libpve-guest-common-perl:amd64 (2.0-16, 2.0-17), samba-common:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), systemd-sysv:amd64 (232-25+deb9u2, 232-25+deb9u4), libldap-common:amd64 (2.4.44+dfsg-5+deb9u1, 2.4.44+dfsg-5+deb9u2), novnc-pve:amd64 (1.0.0-1, 1.0.0-2), libpve-common-perl:amd64 (5.0-33, 5.0-38), libpam-systemd:amd64 (232-25+deb9u2, 232-25+deb9u4), lxc-pve:amd64 (3.0.0-3, 3.0.2+pve1-1), systemd:amd64 (232-25+deb9u2, 232-25+deb9u4), qemu-server:amd64 (5.0-28, 5.0-33), python3-reportbug:amd64 (7.1.7+deb9u1, 7.1.7+deb9u2), openssh-server:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), iproute2:amd64 (4.13.0-3, 4.15.0-5), libsmbclient:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), smbclient:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), openssh-client:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), file:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), ca-certificates:amd64 (20161130+nmu1, 20161130+nmu1+deb9u1), libpve-http-server-perl:amd64 (2.0-9, 2.0-10), pve-kernel-4.15:amd64 (5.2-3, 5.2-6), libpve-apiclient-perl:amd64 (2.0-4, 2.0-5), patch:amd64 (2.7.5-1+b2, 2.7.5-1+deb9u1), base-files:amd64 (9.9+deb9u4, 9.9+deb9u5), tzdata:amd64 (2018c-0+deb9u1, 2018e-0+deb9u1)

Start-Date: 2018-09-18  16:19:26
Commandline: apt full-upgrade
Upgrade: proxmox-widget-toolkit:amd64 (1.0-19, 1.0-20), libpve-storage-perl:amd64 (5.0-25, 5.0-28), pve-container:amd64 (2.0-26, 2.0-27), pve-manager:amd64 (5.2-8, 5.2-9), lxc-pve:amd64 (3.0.2+pve1-1, 3.0.2+pve1-2), qemu-server:amd64 (5.0-33, 5.0-34)
End-Date: 2018-09-18  16:19:41

Code:
Start-Date: 2018-06-15  13:21:49
Commandline: apt-get dist-upgrade
Install: pve-kernel-4.15.17-3-pve:amd64 (4.15.17-12, automatic)
Upgrade: perl-base:amd64 (5.24.1-3+deb9u3, 5.24.1-3+deb9u4), gnupg-agent:amd64 (2.1.18-8~deb9u1, 2.1.18-8~deb9u2), perl-modules-5.24:amd64 (5.24.1-3+deb9u3, 5.24.1-3+deb9u4), zfs-initramfs:amd64 (0.7.8-pve1~bpo9, 0.7.9-pve1~bpo9), pve-firewall:amd64 (3.0-9, 3.0-11), zfsutils-linux:amd64 (0.7.8-pve1~bpo9, 0.7.9-pve1~bpo9), libperl5.24:amd64 (5.24.1-3+deb9u3, 5.24.1-3+deb9u4), pve-i18n:amd64 (1.0-5, 1.0-6), pve-manager:amd64 (5.2-1, 5.2-2), spl:amd64 (0.7.8-pve1~bpo9, 0.7.9-pve1~bpo9), libzfs2linux:amd64 (0.7.8-pve1~bpo9, 0.7.9-pve1~bpo9), novnc-pve:amd64 (0.6-4, 1.0.0-1), libpve-common-perl:amd64 (5.0-31, 5.0-32), gpgv:amd64 (2.1.18-8~deb9u1, 2.1.18-8~deb9u2), qemu-server:amd64 (5.0-26, 5.0-28), libzpool2linux:amd64 (0.7.8-pve1~bpo9, 0.7.9-pve1~bpo9), perl:amd64 (5.24.1-3+deb9u3, 5.24.1-3+deb9u4), libpve-http-server-perl:amd64 (2.0-8, 2.0-9), pve-kernel-4.15:amd64 (5.2-1, 5.2-3), libnvpair1linux:amd64 (0.7.8-pve1~bpo9, 0.7.9-pve1~bpo9), gnupg:amd64 (2.1.18-8~deb9u1, 2.1.18-8~deb9u2), libuutil1linux:amd64 (0.7.8-pve1~bpo9, 0.7.9-pve1~bpo9)
End-Date: 2018-06-15  13:22:46

Start-Date: 2018-09-06  10:07:08
Commandline: apt-get upgrade
Upgrade: proxmox-widget-toolkit:amd64 (1.0-18, 1.0-19), fuse:amd64 (2.9.7-1, 2.9.7-1+deb9u1), libradosstriper1:amd64 (12.2.5-pve1, 12.2.7-pve1), ceph-common:amd64 (12.2.5-pve1, 12.2.7-pve1), libcups2:amd64 (2.2.1-8+deb9u1, 2.2.1-8+deb9u2), linux-libc-dev:amd64 (4.9.88-1+deb9u1, 4.9.110-3+deb9u4), libcurl3:amd64 (7.52.1-5+deb9u6, 7.52.1-5+deb9u7), ceph-mgr:amd64 (12.2.5-pve1, 12.2.7-pve1), ceph-mon:amd64 (12.2.5-pve1, 12.2.7-pve1), libldap-2.4-2:amd64 (2.4.44+dfsg-5+deb9u1, 2.4.44+dfsg-5+deb9u2), libxapian30:amd64 (1.4.3-2, 1.4.3-2+deb9u1), ceph-osd:amd64 (12.2.5-pve1, 12.2.7-pve1), libwbclient0:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), libsystemd0:amd64 (232-25+deb9u2, 232-25+deb9u4), pve-firmware:amd64 (2.0-4, 2.0-5), pve-qemu-kvm:amd64 (2.11.1-5, 2.11.2-1), libcephfs2:amd64 (12.2.5-pve1, 12.2.7-pve1), librbd1:amd64 (12.2.5-pve1, 12.2.7-pve1), pve-docs:amd64 (5.2-4, 5.2-8), openssh-sftp-server:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), pve-firewall:amd64 (3.0-11, 3.0-14), udev:amd64 (232-25+deb9u2, 232-25+deb9u4), ceph-base:amd64 (12.2.5-pve1, 12.2.7-pve1), pve-container:amd64 (2.0-23, 2.0-26), librgw2:amd64 (12.2.5-pve1, 12.2.7-pve1), libmagic1:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), pve-cluster:amd64 (5.0-27, 5.0-30), libudev1:amd64 (232-25+deb9u2, 232-25+deb9u4), python-rados:amd64 (12.2.5-pve1, 12.2.7-pve1), samba-libs:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), dpkg:amd64 (1.18.24, 1.18.25), libmagic-mgc:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), pve-manager:amd64 (5.2-2, 5.2-8), ceph:amd64 (12.2.5-pve1, 12.2.7-pve1), reportbug:amd64 (7.1.7+deb9u1, 7.1.7+deb9u2), pve-kernel-4.15.17-3-pve:amd64 (4.15.17-12, 4.15.17-14), libfuse2:amd64 (2.9.7-1, 2.9.7-1+deb9u1), ssh:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), libpve-guest-common-perl:amd64 (2.0-16, 2.0-17), samba-common:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), systemd-sysv:amd64 (232-25+deb9u2, 232-25+deb9u4), libldap-common:amd64 (2.4.44+dfsg-5+deb9u1, 2.4.44+dfsg-5+deb9u2), novnc-pve:amd64 (1.0.0-1, 1.0.0-2), libgcrypt20:amd64 (1.7.6-2+deb9u2, 1.7.6-2+deb9u3), libpve-common-perl:amd64 (5.0-32, 5.0-38), python-cephfs:amd64 (12.2.5-pve1, 12.2.7-pve1), libpam-systemd:amd64 (232-25+deb9u2, 232-25+deb9u4), lxc-pve:amd64 (3.0.0-3, 3.0.2+pve1-1), systemd:amd64 (232-25+deb9u2, 232-25+deb9u4), qemu-server:amd64 (5.0-28, 5.0-33), python3-reportbug:amd64 (7.1.7+deb9u1, 7.1.7+deb9u2), openssh-server:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), iproute2:amd64 (4.13.0-3, 4.15.0-5), libsmbclient:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), smbclient:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), openssh-client:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), file:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), ca-certificates:amd64 (20161130+nmu1, 20161130+nmu1+deb9u1), pve-edk2-firmware:amd64 (1.20180316-1, 1.20180612-1), libpve-http-server-perl:amd64 (2.0-9, 2.0-10), libdpkg-perl:amd64 (1.18.24, 1.18.25), libpve-apiclient-perl:amd64 (2.0-4, 2.0-5), patch:amd64 (2.7.5-1+b2, 2.7.5-1+deb9u1), librados2:amd64 (12.2.5-pve1, 12.2.7-pve1), libcurl3-gnutls:amd64 (7.52.1-5+deb9u6, 7.52.1-5+deb9u7), base-files:amd64 (9.9+deb9u4, 9.9+deb9u5), dpkg-dev:amd64 (1.18.24, 1.18.25), python-rbd:amd64 (12.2.5-pve1, 12.2.7-pve1), tzdata:amd64 (2018c-0+deb9u1, 2018e-0+deb9u1), python-rgw:amd64 (12.2.5-pve1, 12.2.7-pve1)
End-Date: 2018-09-06  10:08:50

Start-Date: 2018-09-06  16:15:31
Commandline: apt full-upgrade
Install: pve-kernel-4.15.18-4-pve:amd64 (4.15.18-23, automatic), ceph-fuse:amd64 (12.2.7-pve1, automatic)
Upgrade: libpve-storage-perl:amd64 (5.0-23, 5.0-25), pve-kernel-4.15:amd64 (5.2-3, 5.2-7)
End-Date: 2018-09-06  16:16:24

Code:
Start-Date: 2018-08-29  15:40:28
Commandline: apt-get dist-upgrade
Install: libtcmalloc-minimal4:amd64 (2.5-2.2, automatic), ceph-fuse:amd64 (10.2.5-7.2, automatic), libgoogle-perftools4:amd64 (2.5-2.2, automatic), pve-kernel-4.15.18-3-pve:amd64 (4.15.18-22, automatic), libunwind8:amd64 (1.1-4.1, automatic)
Upgrade: proxmox-widget-toolkit:amd64 (1.0-18, 1.0-19), fuse:amd64 (2.9.7-1, 2.9.7-1+deb9u1), libcups2:amd64 (2.2.1-8+deb9u1, 2.2.1-8+deb9u2), linux-libc-dev:amd64 (4.9.88-1+deb9u1, 4.9.110-3+deb9u4), libldap-2.4-2:amd64 (2.4.44+dfsg-5+deb9u1, 2.4.44+dfsg-5+deb9u2), libpve-storage-perl:amd64 (5.0-23, 5.0-25), libxapian30:amd64 (1.4.3-2, 1.4.3-2+deb9u1), libwbclient0:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), libsystemd0:amd64 (232-25+deb9u2, 232-25+deb9u4), pve-firmware:amd64 (2.0-4, 2.0-5), pve-qemu-kvm:amd64 (2.11.1-5, 2.11.2-1), pve-docs:amd64 (5.2-4, 5.2-8), openssh-sftp-server:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), pve-firewall:amd64 (3.0-11, 3.0-14), udev:amd64 (232-25+deb9u2, 232-25+deb9u4), pve-container:amd64 (2.0-23, 2.0-26), libmagic1:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), pve-cluster:amd64 (5.0-27, 5.0-30), libudev1:amd64 (232-25+deb9u2, 232-25+deb9u4), samba-libs:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), dpkg:amd64 (1.18.24, 1.18.25), libmagic-mgc:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), pve-manager:amd64 (5.2-2, 5.2-8), reportbug:amd64 (7.1.7+deb9u1, 7.1.7+deb9u2), pve-kernel-4.15.17-3-pve:amd64 (4.15.17-12, 4.15.17-14), libfuse2:amd64 (2.9.7-1, 2.9.7-1+deb9u1), ssh:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), libpve-guest-common-perl:amd64 (2.0-16, 2.0-17), samba-common:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), systemd-sysv:amd64 (232-25+deb9u2, 232-25+deb9u4), libldap-common:amd64 (2.4.44+dfsg-5+deb9u1, 2.4.44+dfsg-5+deb9u2), novnc-pve:amd64 (1.0.0-1, 1.0.0-2), libgcrypt20:amd64 (1.7.6-2+deb9u2, 1.7.6-2+deb9u3), libpve-common-perl:amd64 (5.0-32, 5.0-38), libpam-systemd:amd64 (232-25+deb9u2, 232-25+deb9u4), lxc-pve:amd64 (3.0.0-3, 3.0.2+pve1-1), systemd:amd64 (232-25+deb9u2, 232-25+deb9u4), qemu-server:amd64 (5.0-28, 5.0-33), python3-reportbug:amd64 (7.1.7+deb9u1, 7.1.7+deb9u2), openssh-server:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), iproute2:amd64 (4.13.0-3, 4.15.0-5), libsmbclient:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), smbclient:amd64 (2:4.5.12+dfsg-2+deb9u2, 2:4.5.12+dfsg-2+deb9u3), openssh-client:amd64 (1:7.4p1-10+deb9u3, 1:7.4p1-10+deb9u4), file:amd64 (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), ca-certificates:amd64 (20161130+nmu1, 20161130+nmu1+deb9u1), pve-edk2-firmware:amd64 (1.20180316-1, 1.20180612-1), libpve-http-server-perl:amd64 (2.0-9, 2.0-10), pve-kernel-4.15:amd64 (5.2-3, 5.2-6), libdpkg-perl:amd64 (1.18.24, 1.18.25), libpve-apiclient-perl:amd64 (2.0-4, 2.0-5), patch:amd64 (2.7.5-1+b2, 2.7.5-1+deb9u1), base-files:amd64 (9.9+deb9u4, 9.9+deb9u5), dpkg-dev:amd64 (1.18.24, 1.18.25), tzdata:amd64 (2018c-0+deb9u1, 2018e-0+deb9u1)
End-Date: 2018-08-29  15:44:17

Start-Date: 2018-09-06  16:16:43
Commandline: apt full-upgrade
Install: pve-kernel-4.15.18-4-pve:amd64 (4.15.18-23, automatic)
Upgrade: pve-kernel-4.15:amd64 (5.2-6, 5.2-7), libcurl3-gnutls:amd64 (7.52.1-5+deb9u6, 7.52.1-5+deb9u7)
End-Date: 2018-09-06  16:17:24

Start-Date: 2018-09-18  16:34:31
Commandline: apt full-upgrade -y
Upgrade: proxmox-widget-toolkit:amd64 (1.0-19, 1.0-20), libpve-storage-perl:amd64 (5.0-25, 5.0-28), pve-container:amd64 (2.0-26, 2.0-27), pve-manager:amd64 (5.2-8, 5.2-9), lxc-pve:amd64 (3.0.2+pve1-1, 3.0.2+pve1-2), qemu-server:amd64 (5.0-33, 5.0-34)
End-Date: 2018-09-18  16:35:07

Don't know what to do. :S
 
I can even reproduce this:

1. Setup three fresh nodes on VirtualBox from ISO "proxmox-ve_5.2-1.iso".
2. Update /etc/hosts and form a pve cluster and restart all nodes
3. Open WebUI on every node and create on one node a testing VM with e.g. live-cd without KVM (i tried "turnkey dokuwiki")
4. Try SPICE to each other and to VM

Result: No matter on which node you are logged on, you can connect to all other nodes and the VM without problems.

Now try the same thing with latest upgrade:
5. Update nodes /etc/apt/sources.list with pve-no-subscription and deactivate the /etc/apt/sources.list.d/pve-enterprise.list
6. Upgrade nodes with apt-get update && apt full-upgrade -y
7. reboot nodes
8. Open WebUI on every node
9. Try to SPICE each other and to VM

Result: You can not connect to other nodes or testing VM via spice. You can connect to VM, if you log into the same node where it is hosted.

In syslog you receive on failure: "spiceproxy: problem with client xxx; Connection reset by peer"

VirtualBox_pve0001_20_09_2018_17_59_47.png VirtualBox_pve0001_20_09_2018_18_00_15.png

VirtualBox_pve0003_20_09_2018_18_00_59.png VirtualBox_pve0003_20_09_2018_18_01_10.png

Code:
remote-viewer.exe --spice-debug "C:\Users\###\Downloads\29MwOGWC.vv"
(remote-viewer.exe:11612): Gtk-WARNING **: Could not find signal handler 'virt_viewer_window_menu_change_cd_activate'.  Did you compile with -rdynamic?
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:285 New session (compiled from package spice-gtk 0.33)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:289 Supported channels: main, display, inputs, cursor, playback, record, usbredir
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usbdk_api.c:62 UsbDk driver is installed.
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usbdk_api.c:86 Loading UsbDk API DLL
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:528 auto-connect filter set to 0x03,-1,-1,-1,0|-1,-1,-1,-1,1
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:2196 Auto-connect disabled, no hider setup needed
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0bf8:1028 (00000000044A9690)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 093a:2510 (00000000044A95B0)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 096e:0006 (00000000044A92D0)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 2a47:f003 (00000000044A9770)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 058f:6387 (00000000044A98D0)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0bda:0184 (00000000044A97B0)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:1736 no migration in progress
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:137 main-1:0: spice_channel_constructed
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:2239 main-1:0: new main channel, switching
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:2610 main-1:0: Open coroutine starting 00000000044ACD80
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:2451 main-1:0: Started background coroutine 00000000044ACC18
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:2173 Missing port value, not attempting unencrypted connection.
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:2477 main-1:0: trying with TLS port
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:2185 main-1:0: Using TLS, port 61000
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:2133 (with proxy http://192.168.100.2:3128)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:2057 proxy lookup ready
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:2040 main-1:0: connecting 0000000008A6FE10...
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:2024 main-1:0: connect ready
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:2379 main-1:0: Load CA, file: (NULL), data: 00000000044AD230
(remote-viewer.exe:11612): GSpice-WARNING **: main-1:0: SSL_connect: error:00000001:lib(0):func(0):reason(1)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:2587 main-1:0: Coroutine exit main-1:0
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:2780 main-1:0: reset
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/channel-main.c:1537 agent connected: no
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:2722 main-1:0: channel reset
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/bio-gio.c:78 bio gsocket destroy
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-channel.c:2328 main-1:0: Delayed unref channel 00000000044ACD80
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:1930 session: disconnecting 0
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:285 New session (compiled from package spice-gtk 0.33)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:289 Supported channels: main, display, inputs, cursor, playback, record, usbredir
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usbdk_api.c:62 UsbDk driver is installed.
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usbdk_api.c:86 Loading UsbDk API DLL
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:528 auto-connect filter set to 0x03,-1,-1,-1,0|-1,-1,-1,-1,1
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:2196 Auto-connect disabled, no hider setup needed
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0bf8:1028 (0000000007190B70)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 093a:2510 (0000000007191010)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 096e:0006 (0000000007190DF0)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 2a47:f003 (0000000007190D90)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 058f:6387 (0000000007190C70)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0bda:0184 (0000000007190970)
(remote-viewer.exe:11612): GSpice-DEBUG: ../../src/spice-session.c:1930 session: disconnecting 0

Code:
remote-viewer.exe --spice-debug "C:\Users\###\Downloads\3CCMhjFx.vv"

(remote-viewer.exe:23944): Gtk-WARNING **: Could not find signal handler 'virt_viewer_window_menu_change_cd_activate'.  Did you compile with -rdynamic?
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:285 New session (compiled from package spice-gtk 0.33)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:289 Supported channels: main, display, inputs, cursor, playback, record, usbredir
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usbdk_api.c:62 UsbDk driver is installed.
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usbdk_api.c:86 Loading UsbDk API DLL
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usb-device-manager.c:528 auto-connect filter set to 0x03,-1,-1,-1,0|-1,-1,-1,-1,1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usb-device-manager.c:2196 Auto-connect disabled, no hider setup needed
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0bf8:1028 (0000000004611ED0)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 093a:2510 (0000000004612730)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 096e:0006 (0000000004612550)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 2a47:f003 (0000000004612510)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 058f:6387 (0000000004612250)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/usb-device-manager.c:1013 device added 0bda:0184 (00000000046128B0)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:1736 no migration in progress
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:137 main-1:0: spice_channel_constructed
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2239 main-1:0: new main channel, switching
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2610 main-1:0: Open coroutine starting 0000000004430490
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2451 main-1:0: Started background coroutine 0000000004430328
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2173 Missing port value, not attempting unencrypted connection.
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2477 main-1:0: trying with TLS port
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2185 main-1:0: Using TLS, port 61000
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2133 (with proxy http://192.168.100.1:3128)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2057 proxy lookup ready
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2040 main-1:0: connecting 0000000008A2FE10...
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2024 main-1:0: connect ready
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2379 main-1:0: Load CA, file: (NULL), data: 00000000046DA0E0
(remote-viewer.exe:23944): Spice-DEBUG: ../../../spice-common/common/ssl_verify.c:400:verify_subject: subjects match
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1302 main-1:0: channel type 1 id 0 num common caps 1 num caps 1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1326 main-1:0: Peer version: 2:2
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1855 main-1:0: spice_channel_recv_link_msg: 2 caps
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1865 main-1:0: got common caps 0:0xB
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1871 main-1:0: got channel caps 0:0x9
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 0 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 1 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 3 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1903 main-1:0: use mini header: 1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1235 main-1:0: channel up, state 3
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2331 set mm time: 894333
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2334 spice_session_set_mm_time: mm-time-reset, old 200359311, new 894333
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-main.c:1662 server name: test
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-main.c:1673 server uuid: ecd4abe6-b8b3-44b7-890f-ad43747637bb
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:137 cursor-4:0: spice_channel_constructed
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display-gst.c:297 GStreamer pipeline: appsrc name=src is-live=true format=time max-bytes=0 block=true caps=image/jpeg ! jpegdec ! videoconvert ! appsink name=sink caps=video/x-raw,format=BGRx sync=false drop=false

(remote-viewer.exe:23944): Spice-WARNING **: ../../src/channel-display-gst.c:303:create_pipeline: GStreamer error: no element "jpegdec"
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:725 GStreamer does not support the mjpeg codec
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display-gst.c:297 GStreamer pipeline: appsrc name=src is-live=true format=time max-bytes=0 block=true caps=video/x-vp8 ! vp8dec ! videoconvert ! appsink name=sink caps=video/x-raw,format=BGRx sync=false drop=false

(remote-viewer.exe:23944): Spice-WARNING **: ../../src/channel-display-gst.c:303:create_pipeline: GStreamer error: no element "vp8dec"
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:731 GStreamer does not support the vp8 codec
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display-gst.c:297 GStreamer pipeline: appsrc name=src is-live=true format=time max-bytes=0 block=true  ! h264parse ! avdec_h264 ! videoconvert ! appsink name=sink caps=video/x-raw,format=BGRx sync=false drop=false

(remote-viewer.exe:23944): Spice-WARNING **: ../../src/channel-display-gst.c:303:create_pipeline: GStreamer error: no element "h264parse"
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:737 GStreamer does not support the h264 codec
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:137 display-2:0: spice_channel_constructed
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:137 inputs-3:0: spice_channel_constructed
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2610 display-2:0: Open coroutine starting 000000000719BBF0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2451 display-2:0: Started background coroutine 000000000719BA88
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2173 Missing port value, not attempting unencrypted connection.
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2477 display-2:0: trying with TLS port
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2185 display-2:0: Using TLS, port 61000
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2133 (with proxy http://192.168.100.1:3128)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2057 proxy lookup ready
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2040 display-2:0: connecting 0000000008C2FE10...
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2024 display-2:0: connect ready
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2379 display-2:0: Load CA, file: (NULL), data: 00000000046DA0E0
(remote-viewer.exe:23944): Spice-DEBUG: ../../../spice-common/common/ssl_verify.c:400:verify_subject: subjects match
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1302 display-2:0: channel type 2 id 0 num common caps 1 num caps 1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1326 display-2:0: Peer version: 2:2
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1855 display-2:0: spice_channel_recv_link_msg: 2 caps
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1865 display-2:0: got common caps 0:0xB
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1871 display-2:0: got channel caps 0:0x52
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 0 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 1 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 3 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1903 display-2:0: use mini header: 1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1235 display-2:0: channel up, state 3
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:915 display-2:0: spice_display_channel_up: cache_size 83886080, glz_window_size 25161728 (bytes)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2610 inputs-3:0: Open coroutine starting 000000000719F0B0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2451 inputs-3:0: Started background coroutine 000000000719EF48
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2173 Missing port value, not attempting unencrypted connection.
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2477 inputs-3:0: trying with TLS port
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2185 inputs-3:0: Using TLS, port 61000
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2610 cursor-4:0: Open coroutine starting 000000000719A8C0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2451 cursor-4:0: Started background coroutine 000000000719A758
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2173 Missing port value, not attempting unencrypted connection.
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2477 cursor-4:0: trying with TLS port
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2185 cursor-4:0: Using TLS, port 61000
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2133 (with proxy http://192.168.100.1:3128)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2133 (with proxy http://192.168.100.1:3128)
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:1656 primary flags: 1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:793 display-2:0: Create primary canvas
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2057 proxy lookup ready
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2040 inputs-3:0: connecting 0000000008E2FE10...
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2057 proxy lookup ready
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2040 cursor-4:0: connecting 000000000902FE10...
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 1 in 0x52: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 1 in 0x52: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:1726 display-2:0: received new monitors config from guest: n: 1/1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:1746 display-2:0: monitor id: 0, surface id: 0, +0+0-640x480
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2024 inputs-3:0: connect ready
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2379 inputs-3:0: Load CA, file: (NULL), data: 00000000046DA0E0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-session.c:2024 cursor-4:0: connect ready
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2379 cursor-4:0: Load CA, file: (NULL), data: 00000000046DA0E0
(remote-viewer.exe:23944): Spice-DEBUG: ../../../spice-common/common/ssl_verify.c:400:verify_subject: subjects match
(remote-viewer.exe:23944): Spice-DEBUG: ../../../spice-common/common/ssl_verify.c:400:verify_subject: subjects match
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1302 inputs-3:0: channel type 3 id 0 num common caps 1 num caps 0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1302 cursor-4:0: channel type 4 id 0 num common caps 1 num caps 0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-display.c:969 display-2:0: display_handle_mark

(remote-viewer.exe:23944): GSpice-WARNING **: Warning no automount-inhibiting implementation available

(remote-viewer.exe:23944): Gtk-WARNING **: Allocating size to SpiceDisplay 000000000728B5E0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1326 inputs-3:0: Peer version: 2:2
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1855 inputs-3:0: spice_channel_recv_link_msg: 2 caps
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1865 inputs-3:0: got common caps 0:0xB
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1871 inputs-3:0: got channel caps 0:0x1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 0 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 1 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 3 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1903 inputs-3:0: use mini header: 1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1326 cursor-4:0: Peer version: 2:2
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1855 cursor-4:0: spice_channel_recv_link_msg: 1 caps
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1865 cursor-4:0: got common caps 0:0xB
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 0 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 1 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:2835 test cap 3 in 0xB: yes
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1903 cursor-4:0: use mini header: 1
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1235 cursor-4:0: channel up, state 3
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/spice-channel.c:1235 inputs-3:0: channel up, state 3
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/channel-cursor.c:308 cursor-4:0: set_cursor: flags 1, size 0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/decode-glz.c:373 decode_header: 32x6, id 0, ref 0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/decode-glz.c:373 decode_header: 32x10, id 1, ref 0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/decode-glz.c:373 decode_header: 32x10, id 2, ref 0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/decode-glz.c:373 decode_header: 32x10, id 3, ref 0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/decode-glz.c:373 decode_header: 32x6, id 4, ref 0
(remote-viewer.exe:23944): GSpice-DEBUG: ../../src/decode-glz.c:373 decode_header: 32x10, id 5, ref 0

I also noticed, if you try to connect from a different node multiple times (with pause in between), there could be a chance like 2 out of 10 that connection will establish. :O

Connection has been tested from Windows 10 1803 with Virt-Viewer v6.
 
Good evening,
I believe that I am facing the same problem after the last update I made.
Spice does not work on any other host other than the one I have done login.
Ιn my other hosts I see the message "Unable to connect to the graphics server", although I did the process of re-issuing new certificates according to the help page of the proxmox on all hosts and reboot all, the problem has not been solved.
I have tried many versions of the remote-viewer ( spice client ) and different machines and os and the problem was not solved.

Please, if there is someone who can help me solve the problem!

Thanks, Dimitris
 
Also some update along the way makes USB redirection not working anymore (single pve node). I've try it with latest spice guest tools and virt-viewer and browsing USB drive from guest is very slow or remote-viewer freeze/crash (win10 guest 64bit, win7 guest 32bit).

Anyway I will install pve5.2 from iso on fresh node for test.o_O
 
Last edited:
Also some update along the way makes USB redirection not working anymore (single pve node). I've try it with latest spice guest tools and virt-viewer and browsing USB drive from guest is very slow or remote-viewer freeze/crash (win10 guest 64bit, win7 guest 32bit).

Anyway I will install pve5.2 from iso on fresh node for test.o_O If aint microsoft...then is somebody else...its like neverendingstory with these systems and softwares...:)
 
I think the problem is related to certification, somewhere there I think it's the fault and I can not do something about it.
I will wait for the test results from installation 5.2 and I will do it if I do well.
 
Also some update along the way makes USB redirection not working anymore (single pve node). I've try it with latest spice guest tools and virt-viewer and browsing USB drive from guest is very slow or remote-viewer freeze/crash (win10 guest 64bit, win7 guest 32bit).

Anyway I will install pve5.2 from iso on fresh node for test.o_O If aint microsoft...then is somebody else...its like neverendingstory with these systems and softwares...:)

I think the problem is related to certification, somewhere there I think it's the fault and I can not do something about it.
I will wait for the test results from installation 5.2 and I will do it if I do well.
 
Thank you, seems to be working again after upgrading the package mentioned. Restart was not necessary.
 
Sorry for my English. I have a similar problem with spice. When it was the installed version of Proxmox 5.3.5 everything worked but after upgrading to 5.3.7 I can not connect to the machines. If I set the graphic as the default, then I can connect to the machine via VirtViewer, but if I set the QLX then there is no connection. Certificates created again. 3 machines And the same problem.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!