I am running Boxes on a Fedora 22 host. I've noticed that guests are consistently hanging while doing this: 1) Create a Fedora 22/21/CentOS 7 guest (these are the guests I can reproduce this problem with so far). 2) Boot to GDM 3) Pause the machine (save state to disk) 4) Resume After step 4th the graphical session of the guest is frozen and there's no option but to reboot. The SPICE client used seems to be irrelevant in this case, this happened consistently in Boxes, virt-manager and using spicy as well.
Can be reproduced with virsh managedsave/start and virt-viewer, does not seem to be related to, happens with VNC and VGA (though VNC + QXL gave me some weird failure when trying to restore), seemed to went away when removing the smartcard node. Still possible to login through ssh when it's hung
I played more with that, removing the <input type="mouse" bus="usb"> node from the VM definition seems to stop this from occurring.
Forgot to mention, this happens without anything SPICE related in the VM XML definition (no spicevmc channel, no usbredir channel, vga instead of qxl, and VNC instead of SPICE). I boot a f22 guest to GDM, connect to it with virt-viewer. In GDM, I choose "User is not listed here" in order to get a text entry where I cant test typing. Then virsh managedsave/virsh start, and I can no longer input more text. I think alt-tab-switching to virt-viewer right after issuing virsh start helps to trigger the hang. Given that this can be reproduced without SPICE, this bug is not filed in the right place.
(In reply to Christophe Fergeau from comment #3) > Forgot to mention, this happens without anything SPICE related in the VM XML > definition (no spicevmc channel, no usbredir channel, vga instead of qxl, > and VNC instead of SPICE). I boot a f22 guest to GDM, connect to it with > virt-viewer. In GDM, I choose "User is not listed here" in order to get a > text entry where I cant test typing. Then virsh managedsave/virsh start, and > I can no longer input more text. I think alt-tab-switching to virt-viewer > right after issuing virsh start helps to trigger the hang. > > Given that this can be reproduced without SPICE, this bug is not filed in > the right place. Yeah, I completely agree. Sorry for the wrong guessing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.