Re: save image file format? and [RFC] tmem save/restore/migrate

[Stefano Stabellini <stefano.stabellini@eu.citrix.com>]

John Levon wrote:

> On Thu, Jun 18, 2009 at 09:51:58AM +0100, Tim Deegan wrote:
> 
>> It's still the ad-hoc stream-of-data format, I'm afraid.  The whole
>> format needs a good kicking.  It's not even portable between 32-bit and
>> 64-bit tools.  Gianluca (Cc'd) is just starting to look at the
>> save/restore code in the hopes of making it more sane, so now would be a
>> good time to bring up any suggestions.
> 
> One possibility Anthony Liguori brought up before is using all of qemu's
> container format. I'm not sure it's ever feasible to make it fully
> compatible, but it certainly seems like an obvious choice to use as a
> base. Unfortunately, I think it's defined-by-the-code as well.
> 

At least in theory is certainly feasible: just a matter or registering
another savevm function for a record called "cpu" or "vcpu", that would
take care of saving the guest memory using xc_domain_save.

The qemu people are also maintaing save record compatibility now, so we
are safe from that perspective.