Re: [libvirt-users] Qemu restore error

On 12/15/2011 08:48 AM, Dennis Householder wrote: This is the correct list; the error message comes from libvirt's qemuDomainSaveImageOpen() method, and implies that you have a corrupted save file (save files are created by 'virsh save' to a user-specified location, or by 'virsh managedsave' to a libvirt-maintained location; the libvirt-guests init script uses virsh managedsave as part of host shutdown). Are you restoring via 'virsh restore path/to/file', or are you just trying to start the guest with 'virsh start' or a similar action in virt-manager? If the former, then path/to/file is indeed corrupt; can you show us the size of that file, as well as 'od -N 128 -tx1z path/to/file'? If the latter, then you've uncovered a bug in the managedsave code (which I will be fixing shortly) - we attempt to detect and unlink corrupt managedsave files automatically, but in looking at the code, I see I missed a code path - if the file is corrupt because it is too short, then we fail to do the unlink(), making the problem perpetual. If this is the case, then please give me the same output as requested in the previous paragraph, but using /var/lib/libvirt/qemu/save/<dom>.save as the path/to/file. Then, after you have given me the details, you can work around the problem by doing 'virsh start --force' to force a fresh boot (the save file is already corrupt, so there is unfortunately no way to get the runtime state of the guest back to what it was when you suspended your host); hopefully your guest can fsck and recover gracefully from what was in the virtual disks at the time of the host suspend. -- Eric Blake eblake(a)redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org