WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] save image file format? and [RFC] tmem save/restore/migr

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] save image file format? and [RFC] tmem save/restore/migrate
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Thu, 18 Jun 2009 13:02:41 +0100
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Gianluca Guida <Gianluca.Guida@xxxxxxxxxxxxx>
Delivery-date: Thu, 18 Jun 2009 04:59:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090618113924.GB17990@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <f832a6fa-b148-41f2-baa3-d987ecfb2a55@default> <20090618085158.GE16056@xxxxxxxxxxxxxxxxxxxxx> <20090618113924.GB17990@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (X11/20080505)
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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel