Virt-Viewer not connecting when spice-vdagent is isntalled

[Mave95]

Hi,

SPICE is only working, when spice-vdagent is not installed. With spice-vdagent installed the Virt-Viewer can't connect and stops responding. Some distros automatically ship with spice-vdagent, so I have to remove it via the NoVNC Console to get SPICE working. I just enable SPICE via Hardware->Display->Graphic card->SPIC in my VMs. Is this normal behavior or am I missing some configuration.

Best Regards

 

[aaron]

This is definitely not normal behavior. Without the spice-vdagent you will not have the resolution changed to the windows size of the remote viewer and automatic mouse release might also not work seamlessly.

What guests do you run?

 

[Mave95]

This is definitely not normal behavior. Without the spice-vdagent you will not have the resolution changed to the windows size of the remote viewer and automatic mouse release might also not work seamlessly.

What guests do you run?

Debian, Manjaro, Pop!_OS, ... They all behave the same.

 

[tom]

Debian, Manjaro, Pop!_OS, ... They all behave the same.

Also depends on the used display manager - e.g. using Gnome works great.

 

[Mave95]

Also depends on the used display manager - e.g. using Gnome works great.

Pop!_OS and my Manjaro installation use Gnome, but still won't work with spice-vdagent installed.

 

[tom]

I just installed a default manjaro gnome edition, just works.

I connect using the remote viewer 7.0 from my Debian Buster Workstation.

 

[Mave95]

I just installed a default manjaro gnome edition, just works.

I connect using the remote viewer 7.0 from my Debian Buster Workstation.

Just checked with virt-viewer on Arch and it's working. It seems to be a problem with the Windows build of virt-viewer. Thanks for your help.

 

[tom]

It seems to be a problem with the Windows build of virt-viewer

which version? try a newer (or older) one.

 

[Mave95]

Version 8.0 is working. 9.0 isn't.

 

[tom]

Version 8.0 is working. 9.0 isn't.

Can you report this to the virt-viewer team, seems like a client issue?

https://virt-manager.org/bugs/#view