Red Hat Bugzilla – Bug 837236
If managed restore fails, offer to discard state and start normally
Last modified: 2016-01-31 20:56:47 EST
I sometimes experience the following issue (probably triggered by seldom kernel hangs/crashes due to a high system uptime).
Some of the virtual machines get into a saved state and can't be restored or started again. After several painful restorations in form of machine cloning/deletion I found out, that there's a zero sized save file in /var/lib/libvirt/qemu/save that just needs to be deleted and that's all. I believe there should be a menu entry for discarding the machine saved state (especially when it's corrupted and can't be restored).
Please, add a new menu entry triggering a confirmation dialog for the save file deletion.
Thanks in advance.
If a guest fails to start with a saved image, we should provide a follow up dialog like 'Guest could not be started from the saved state. Would you like to discard the saved state and start fresh?' or similar.
virt-manager-0.9.3-1.fc16 has been submitted as an update for Fedora 16.
virt-manager-0.9.3-1.fc17 has been submitted as an update for Fedora 17.
* 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.3-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
virt-manager-0.9.4-1.fc17 has been submitted as an update for Fedora 17.
virt-manager-0.9.4-1.fc16 has been submitted as an update for Fedora 16.
virt-manager-0.9.4-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
virt-manager-0.9.4-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.