Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: dibl on 2016/07/30, 16:10:10
-
After today's removal of gir1.2-spice-client-gtk-2.0:amd64 during d-u, my KVM VM won't display -- the spice-server video display crashes. Investigation indicates there is a transition of some of the related libraries and packages.
https://release.debian.org/transitions/html/auto-spice-gtk.html (https://release.debian.org/transitions/html/auto-spice-gtk.html)
So no spice-client VM until the transition goes through, FYI.
-
2.5 months later .... Good News! Today's d-u pulled in updated gir1.2-spice-client and other needed packages and finally the KVM VM can be run with the spice-client display once again.
-
Where was the problem - we use spice on a daily base without problems?
-
I'm no expert on how it works, but when gir1.2-spice-client-gtk-2.0:amd64 was removed, it was not immediately replaced, and the VM display crashed as soon as I started the VM. The VM was running, as shown in the KVM manager, but no display. When I saw the new spice packages come in yesterday, I gave it a try, and it is working correctly again.
Perhaps there's something about the setup that I was missing, if you were able to keep it running. Are you using spice on a KDE desktop?
-
hello dibl,
the team seems to prefer /usr/bin/remote-viewer which comes with the virt-viewer package. On installation it will register the spice://-protocol and so we can share such links in our dev-channel and open it with a simple click: spice://server:port .
I didn't see your issue on my cinnamon host.
greetings
musca
-
Ahhhhhhh - thanks musca! I feel slightly less stupid now. I should learn to use remote-viewer, I guess, but now I don't need to. ;D