[SOLVED] Virt-viewer issue, advice needed for filing bug

[aPollO]

I can confirm this for latest Fedora 28 virt-viewer and latest Windows virt-viewer build (7.0). I will submit this in the bug ticket.

I read that downgrading on Fedora 28 works. Maybe on SUSE, too.
Working versions in Fedora:

spice-glib 0.34-4.fc28
spice-gtk3 0.34-4.fc28
virt-viewer 6.0-3.fc28

 

[loomes]

i can confirm that virt-viewer 7.0-256 x64 for windows also not working with proxmox 5.2!
Downgrade virtviewer to v6 and all is working fine again.

 

[aPollO]

Yep downgrade to virt-viewer 6.0 on windows or just do a

dnf downgrade spice-glib virt-viewer

on fedora 28 will bring back a working version. Some users on the Red Hat Bugtracker guess that this issue is related to changes happened between the version 0.34 and 0.35 of spice-glib. They switched from a own copy of wocky-http to the one of glibc. And with this change the support of TLS 1.0 is removed now. Can it be that proxmox still use old TLS version or chipher suits?

 

[dcsapak]

Can it be that proxmox still use old TLS version or chipher suits?

i played a little with it ( also wrote on the redhat bugtracker) and the tls is definitely not the cause

i guess there is something wrong with the proxy handling, but i cannot say yet if its our fault, or the one of spice-gtk/remote-viewer

 

[dcsapak]

just an update: i found the problem (within our spiceproxy) patch here: https://pve.proxmox.com/pipermail/pve-devel/2018-August/033418.html

 

[aPollO]

Already read this. Hope the patch will be merged in the enterprise repository soon Thank you very much Dominik.

 

[loomes]

I changed the file and restart pvedaemon.service, but Virtviewer v7 dont work.

 

[aPollO]

I think you have to restart spiceproxy as well. Maybe pve-manager, too.

 

[loomes]

Ohhh sure, restart spiceproxy and all is good

 

[janssensm]

libpve-http-server-perl: 2.0-10 from enterprise repo fixed it, marking thread as solved. Thanks.