Created attachment 888312 [details] garbled first time Description of problem: First time I take a snapshot of a newly created Ubuntu 14.04 Desktop VM I'm setting up, the screenshot is garbled. Second (and thereafter) snapshot's screenshot looks fine. Version-Release number of selected component (if applicable): 1.0.0-5.fc20 How reproducible: Always, on new vms at least. But then the second snap is fine. Steps to Reproduce: 1. Create a new VM 2. Install Ubuntu 14.04 Desktop 64 bit 3. After OS is installed, take a snapshot. Actual results: Screenshot image is garbled Expected results: Screenshot image should be good Additional info: See attached screenshots. (Took from two different vms, but the problem did happen on both.) Installed components: virt-manager.noarch 1.0.0-5.fc20 installed virt-manager-common.noarch 1.0.0-5.fc20 installed libvirt.x86_64 1.1.3.4-1.fc20 installed <snip> libvirt-client.x86_64 1.1.3.4-1.fc20 installed libvirt-daemon.x86_64 1.1.3.4-1.fc20 installed libvirt-daemon-kvm.x86_64 1.1.3.4-1.fc20 installed libvirt-gconfig.x86_64 0.1.7-2.fc20 installed libvirt-glib.x86_64 0.1.7-2.fc20 installed libvirt-gobject.x86_64 0.1.7-2.fc20 installed libvirt-python.x86_64 1.1.3.4-1.fc20 installed qemu-common.x86_64 2:1.6.1-3.fc20 installed qemu-guest-agent.x86_64 2:1.6.1-3.fc20 installed qemu-img.x86_64 2:1.6.1-3.fc20 installed qemu-kvm.x86_64 2:1.6.1-3.fc20 installed qemu-system-x86.x86_64 2:1.6.1-3.fc20 installed
Created attachment 888313 [details] ok second time
I should mention that I'm connecting to the host via xrdp. And I should clarify that I don't need to actually create the snapshot. If I close the dialog and re-open, that makes the garbled image go away (so just refreshing that image pull, I guess.)
I can reproduce this too, though on plain f20 host with an f20 guest: the screenshot isn't garbled like yours, but it shows the old vga content before transitioning to plymouth/gdm. I've sent a patch upstream to qemu-devel that fixes this for me
Okay, looks like my patch was no good: https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg03840.html The proper solution requires new qemu APIs and libvirt coordination, so is quite a ways off. In the meantime we should just work around this in virt-manager, so reassigning.
I filed a qemu bug for the root upstream issue: https://bugs.launchpad.net/qemu/+bug/1314293 But I've pushed a virt-manager patch to work around this now: commit 2272166844f84943342fc097af927a09737ee57f Author: Cole Robinson <crobinso> Date: Tue Apr 29 13:26:26 2014 -0400 snapshots: Fix screenshot with qxl+spice (bz 1089780)
virt-manager-1.0.1-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/virt-manager-1.0.1-3.fc20
Package virt-manager-1.0.1-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virt-manager-1.0.1-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-5846/virt-manager-1.0.1-3.fc20 then log in and leave karma (feedback).
virt-manager-1.0.1-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.