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: Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] save image file format? and [RFC] tmem save/restore/migrate
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Thu, 18 Jun 2009 13:05:58 +0100
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Gianluca Guida <Gianluca.Guida@xxxxxxxxxxxxx>, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 18 Jun 2009 05:06:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A3A2CE1.2010100@xxxxxxxxxxxxx>
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> <4A3A2CE1.2010100@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.17 (2007-11-01)
At 13:02 +0100 on 18 Jun (1245330161), Stefano Stabellini wrote:
> 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.

Yuck.  You still need to add a bunch of metadata from xend that qemu
doesn't know about, so you'll have to wrap the qemu output in another
file format already.  Wrapping the memory image inside qemu's image is
just layering for its own sake.  (Also, using qemu to save a PV guests 
would be pretty wierd).

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

Yes, but their code-defines-format model is rubbish.  I've written a
couple of tools that parse HVM save file info based on the Xen public
headers; doing the same for a qemu-style implicit format is a PITA.

Tim.

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 0DZ, UK.]

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

<Prev in Thread] Current Thread [Next in Thread>