Description of problem: When using virt-manager with a guest setup with display set to spice and video set to QXL the console does not show anything, only a message "Connecting to graphical console for guest". When switching video to cirrus for example, only a black screen appears. Setting display to VNC does work. Version-Release number of selected component (if applicable): 0.12.1 How reproducible: Update spice-gtk (and dependencies) to 0.12.1 Steps to Reproduce: 1. Create a KVM guest in virt-manager 2. Choose spice for display 3. Choose QXL for video Actual results: "Connecting to graphical console for guest" Expected results: The graphical console Additional info: When downgrading to 0.11-4, all is well again.
Argh, I missed this case when Daniel rewrote the URI parser: (virt-manager:6024): GSpice-WARNING **: Missing port or tls-port in spice URI 'spice://localhost?port=5900'
Patch sent to Spice ML.
I figured it had to be something relatively easy to fix. Thanks for the quick response. Anxiously awaiting the fixed packages ...
Fix in: http://koji.fedoraproject.org/koji/taskinfo?taskID=4044748
Confirmed, works like a charm!
spice-gtk-0.12-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/spice-gtk-0.12-2.fc17
spice-gtk-0.12-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/spice-gtk-0.12-3.fc17
spice-gtk-0.12-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
This seems to be a problem again in Fedora 19 alpha: the same graphics settings (which are the default) result in a black virt guest display and a runaway virt process that pins 100% of the number of allocated cores.
(In reply to comment #9) > This seems to be a problem again in Fedora 19 alpha: the same graphics > settings (which are the default) result in a black virt guest display and a > runaway virt process that pins 100% of the number of allocated cores. I suggest you open a bug to the appropriate client for further triaging, please give more details! and try to get a backtrace of the 100% cpu process to see where it is spinning. and perhaps some log would be useful too.