Description of problem: Attempt to use spice instead of vnc from virt-manager gives the following error: >> Cannot display graphical console type 'spice': No module named SpiceClientGtk <<< Version-Release number of selected component (if applicable): [root@maverick ~]# rpm -q kernel kernel-2.6.38.2-9.fc15.x86_64 [root@maverick ~]# rpm -qa |grep virt libvirt-client-0.8.8-4.fc15.x86_64 libvirt-0.8.8-4.fc15.x86_64 virt-viewer-0.3.1-1.fc15.x86_64 virt-top-1.0.5-2.fc15.x86_64 virt-mem-0.3.1-9.fc12.x86_64 python-virtinst-0.500.6-2.fc15.noarch libvirt-python-0.8.8-4.fc15.x86_64 virt-manager-0.8.7-3.fc15.noarch [root@maverick ~]# rpm -qa |grep spice spice-glib-0.5-6.fc15.x86_64 spice-gtk-0.5-6.fc15.x86_64 spice-client-0.8.0-2.fc15.x86_64 spice-protocol-0.8.0-1.fc15.noarch spice-server-0.8.0-2.fc15.x86_64 [root@maverick ~]# How reproducible: Always Steps to Reproduce: 1. Upgrade from F14 to F15 beta [with preupgrade-cli] 2. Change one of the kvm VM config from VNC to SPICE [via virt-manager] 3. Start the kvm VM [via virt-manager] 4. Attempt to connect to the graphical console [via virt-manager] Actual results: Get the following error message in the graphical console window [of virt-manager] >> Cannot display graphical console type 'spice': No module named SpiceClientGtk <<< Expected results: access to graphical console via spice Additional info: I'm able to connect to the spice console directly with 'spicec -h localhost -p 5901'. I'm also seeing this error when I try connecting to this VM from a remote F14 box [with virt-manager-0.8.7-2.fc14.noarch via ssh], and I'm able to connect directly with 'spicec' [again via ssh] And my access to the vm via vnc works fine [both locally on the F15 box, and remotely from the F14 box]
Ah - found #696638 "yum install spice-gtk-python" fixes the problem on both F14 and F15 boxes either proper rpm dependencies or better help message [on which rpm to install] would be good.
*** Bug 696638 has been marked as a duplicate of this bug. ***
urgh, virt-manager had an incorrect dep on spice-gtk, not spice-gtk-python.
virt-manager-0.8.7-4.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/virt-manager-0.8.7-4.fc15
Package virt-manager-0.8.7-4.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virt-manager-0.8.7-4.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/virt-manager-0.8.7-4.fc15 then log in and leave karma (feedback).
[checked the F15 update and added karma] Also - Could you also push this update to F14 aswell?
We aren't having virt-manager in f14 depend on the spice client, because f14 qemu and libvirt don't work well together out of the box.
I'm using kvm VMs on F15 - and virt-manager from F14. With the virt-manager-0.8.7 update to F14 -I'm able to configure all spice related things on the remote F15 VMs- except for "No module named SpiceClientGtk" error - which got fixed by installing "spice-gtk-python" [on F14]. So I think its appropriate for F14 to have this update [as its a client side functionality]. The server side functionality wrt qemu probably needs a protocol fix.. [i.e virt-manager should check with libvirtd - if it supports spice or not - and then display appropriate options to the user] [well - if I attempt to change f14 vm settings from vnc to spice - I get the following error anyway: libvirtError: internal error unknown graphics device type 'spice' so perhaps thats a sufficient error message for F14]
> The server side functionality wrt qemu probably needs a protocol fix.. [i.e > virt-manager should check with libvirtd - if it supports spice or not - and > then display appropriate options to the user] The QEMU in F14 contains a set of non-upstream, incomplete patches for SPICE. F15 is the first QEMU which has remotely usable SPICE support.
virt-manager-0.8.7-4.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
This problem either persisted or there was a regression... on a newly installed Fedora 17 system I got the same error, and upon finding and reading this bug was able to resolve it with "yum install spice-gtk-python".
The bottom line is that virt-manager still doesn't correctly depend on spice-gtk-python. This bug should be re-opened.
Indeed I just ran into this as well on Fedora 17. This problem is still/again present.
i felt free to reopen this bug because it is still or again present in fedora 17.
Me too affected by tis bug with F17 and solved installing spice-gtk-python
*** Bug 829002 has been marked as a duplicate of this bug. ***
I verified this is fixed with the latest virt-manager version in F17, spice-gtk-python is correctly pulled in as a dependency, and new guests on a freshly installed machine use spice.