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

[Nicolas Sebrecht]

The 27/07/11, 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.

I'm stuck!

As told before, I have one working (in production) system and others
failing Gentoo systems (including the testing machine).

I've check the working system against the testing machine and looked for
differences. I did remove differences one by one (luckily systems are
very near from each other) and couldn't have the testing machine to
work.

I've check Linux kernel configuration (first) and the whole system for
installed packages and compilation options. On each difference found
I've done:
- compilation and reinstallation of ALL the packages;
- reboot;
- tests.

Now, I have almost two exact same systems behaving differently. Some
minor differences remain about installed packages (missing on testing):
- lshw
- pv
- colorgcc
- autofs
- iperf

Hardware isn't the same, though. Main differences are:
- Intel(R) Xeon(R) CPU E5420  @ 2.50GHz (cpu family : 6)
  hardware RAID
- Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz (cpu family : 6)
  software RAID

Ouch!

-- 
Nicolas Sebrecht