From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: save image file format? and [RFC] tmem save/restore/migrate Date: Thu, 18 Jun 2009 13:02:41 +0100 Message-ID: <4A3A2CE1.2010100@eu.citrix.com> References: <20090618085158.GE16056@york.uk.xensource.com> <20090618113924.GB17990@movementarian.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090618113924.GB17990@movementarian.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Levon Cc: Tim Deegan , Dan Magenheimer , "Xen-Devel (E-mail)" , Gianluca Guida List-Id: xen-devel@lists.xenproject.org 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.