Description of problem: Creating a guest with all defaults leads to a vnc/cirrus diplay, wich suffer from slowness and high cpu comsupmtion (it started one month before F13 was EOLed). Anyway, spice/qlx is much better. Version-Release number of selected component (if applicable): libvirt.x86_64 0.8.8-7.fc15 @updates libvirt-client.x86_64 0.8.8-7.fc15 @updates libvirt-python.x86_64 0.8.8-7.fc15 @updates virt-manager.noarch 0.8.7-6.fc15 @updates virt-viewer.x86_64 0.3.1-1.fc15 @fedora How reproducible: allways Steps to Reproduce: 1. create a guest 2. it defaults to vnc/cirrus Actual results: vnc/cirrus is the display Expected results: spice/qlx being the display Additional info: wnload drivers that are offered only in .zip and not in .iso
Additional info: The drivers are offered only in .zip and not in .iso (wich can be directly added to the guest more easy) I hit "summit..." too early by mistake.
Thanks for the report. This is the default in f16 but we won't be changing it in f15 at this point since most of the qxl/spice testing has been on f16. Closing as WONTFIX
Is the qxl/spice really default in Fedora 16? My virt-manager defaults to vnc/cirrus. After the recent change in cirrus driver, it breaks KDE desktop (the Qt raster engine does not support 16 bpp very well). See https://bugzilla.redhat.com/show_bug.cgi?id=810161
Yeah this is actually busted. Moving to f17
virt-manager-0.9.1-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/virt-manager-0.9.1-3.fc17
Package virt-manager-0.9.1-3.fc17: * should fix your issue, * was pushed to the Fedora 17 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.9.1-3.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6651/virt-manager-0.9.1-3.fc17 then log in and leave karma (feedback).
virt-manager-0.9.1-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
Not fixed in 0.9.1-3. I just created a new f17 guest and (1) the default is still cirrus+vnc, (2) the package doesn't install the proper dependencies and manually changing to spice results in Cannot display graphical console type 'spice': No module named SpiceClientGtk $ rpm -q -a | grep spice spice-gtk3-0.12-4.fc17.x86_64 spice-vdagent-0.10.1-1.fc17.x86_64 spice-glib-0.12-4.fc17.x86_64 spice-gtk-0.12-4.fc17.x86_64 spice-server-0.10.1-2.fc17.x86_64 $ rpm -q -a | grep virt virt-manager-common-0.9.1-3.fc17.noarch libvirt-daemon-0.9.11.3-1.fc17.x86_64 libvirt-0.9.11.3-1.fc17.x86_64 libvirt-python-0.9.11.3-1.fc17.x86_64 libvirt-daemon-config-network-0.9.11.3-1.fc17.x86_64 libvirt-client-0.9.11.3-1.fc17.x86_64 virt-manager-0.9.1-3.fc17.noarch libvirt-daemon-config-nwfilter-0.9.11.3-1.fc17.x86_64 python-virtinst-0.600.1-1.fc17.1.noarch
Yes, F17 still creates cirrus+vnc by default. Too bad, since i was not able to locate winxp qlx drivers anymore...only source code. discontinued?
I think this is a side effect of missing spice dependency *** This bug has been marked as a duplicate of bug 819270 ***