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/
Home Products Support Community News


Re: [Xen-devel] HVM save/restore issue

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] HVM save/restore issue
From: "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>
Date: Tue, 20 Mar 2007 16:46:52 +0800
Cc: Tim <Tim.Deegan@xxxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>
Delivery-date: Tue, 20 Mar 2007 01:51:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2254BEA.4A20%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070320081236.GJ21485@xxxxxxxxxxxxxxxxxxxxxx> <C2254BEA.4A20%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
On Tue, Mar 20, 2007 at 08:29:30AM +0000, Keir Fraser wrote:
> On 20/3/07 08:12, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx> wrote:
> > latest HVM save/restore break again:(
> > 
> > i use the memsize(the number in the xmexample.hvm) deduced from
> > 'memory_static_min' to calculate some HVM PFNs when restore.
> Out of interest: why would you do this? I glanced upon the code you are
> referring to in xc_hvm_restore.c yesterday, and it struck me as particularly
> gross. All three PFNs (ioreq, bufioreq, xenstore) could be saved in the
> store after building the domain and then saved/restored as part of the
> Python-saved data. The situation is easier than for a PV guest because PFNs

save all PFNs directly is good idea. i have this code to keep create and 
process similar.
i'd like directly save/restore all pfns in xc_hvm_{save,restore}. is this your 

> do not change across save/restore.
> The more assumptions about memory layout we bake into xc_hvm_{save,restore}
> now, the more we have to unbake when the HVM memory map becomes more dynamic
> (balloon driver support, in particular). Making these assumptions to some
> extent for now is okay, but we should avoid it where possible.
>  -- Keir

best rgds,

Xen-devel mailing list