Re: libvirt-0.9.1 to 0.9.3-r1: managedsave/save won't start/restore at saved state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/27/2011 04:37 AM, Nicolas Sebrecht wrote:
I'm seeing strange behaviour, here.  Any guests saved using both
managedsave and save commands from virsh won't restore at saved state. A
new full boot sequence happen.

- Tested against libvirt v0.9.1, v0.9.2, v0.9.3-r1 (Gentoo)
- Confirmed on three different hosts Gentoo amd64 systems.
- Tested with gentoo and ubuntu guests.
- Nothing relevant in /var/log/libvirt/libvirt.log or
/var/log/libvirt/qemu/<dom>.log

The "state file" /var/lib/libvirt/qemu/save/<dom>.save exists and is
deleted when 'virsh start' is called.

The new boot sequence is confirmed by :
- VNC console checks
- previous screen sessions lost
- uptime

I've open a bug at https://bugs.gentoo.org/show_bug.cgi?id=376333 but
had no answer.

Any idea on what could happen or how to inspect it?

If you pause ("virsh suspend") the guest before the save, can you then successfully start the domain (it should "start" in a paused state, and when the virsh commandline returns to the prompt, you can resume it with "virsh resume".) If this is the case, it could be a race condition within qemu.

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]