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-users

[Xen-research] Re: [Xen-users] xm save -c

To: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Subject: [Xen-research] Re: [Xen-users] xm save -c
From: "Mike Sun" <msun@xxxxxxxxxx>
Date: Fri, 14 Nov 2008 13:39:01 -0500
Cc: fabigant@xxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, xen-research@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 14 Nov 2008 10:39:05 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=jRv/HC91f/vzz0HncRZX3u2dKp6mlKqIyEwMzeJeOe4=; b=T1luw+3Sjw5Jra7jrxmvpaq1MnA1zgwdt8RK7BW7stLPJauKGNPlAXDGnf0McPTWuM XMHTmihCXt9jkoRD6KYKIhfL6Z5e1L3J38dvRPpH3bh/6nZM9fblNw7tTj3FNmwMOqbb agniZZ+SOR9yLBYi+6+KQukqCeucKECIJp2sY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=MTYagRB0qpn7iejNhHUYAJITxDTuDvb9LQHpNHztSjlUHAZHuyBqiRo2LkLu2u8Y+K 5TYinq3snoMjNGQM0vwG2paBK6p+ZHYqiXv8QlhZe7qEua1ojlRCYmrITDJpBwUgowSL 5N0rkd0xVZHoa/VZsv8X95obKjhDwSiQTl95k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <e4e579070811141035h136d3171w6bcb57a890d5f62@xxxxxxxxxxxxxx>
List-help: <mailto:xen-research-request@lists.xensource.com?subject=help>
List-id: Research Issues on Xen <xen-research.lists.xensource.com>
List-post: <mailto:xen-research@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-research>, <mailto:xen-research-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-research>, <mailto:xen-research-request@lists.xensource.com?subject=unsubscribe>
References: <491D5177020000B10000592A@xxxxxxxxxxxxxxxxxxxxx> <491D523B0200009900030FA4@xxxxxxxxxxxxxxxxxxxxx> <e4e579070811141035h136d3171w6bcb57a890d5f62@xxxxxxxxxxxxxx>
Sender: xen-research-bounces@xxxxxxxxxxxxxxxxxxx
Whoops, forgot to mention this is a patch for Xen 3.2.2, though I'm
sure the changes can be applied to unstable.

On Fri, Nov 14, 2008 at 1:35 PM, Mike Sun <msun@xxxxxxxxxx> wrote:
> The modification to do a checkpoint using the live migration mechanism
> of pre-copying is a trivial one and just something we're benchmarking
> against with our CoW solution.  Here's a patch that changes 'xm save
> -c' to do the checkpoint using the live migration mechanism instead of
> the default way.  Word of warning: it's a hack and I haven't made the
> changes necessary so that the checkpoint file won't contain the pages
> copied during the copy rounds so the checkpoint file will be much
> larger than necessary.
>
> I'm not sure why a checkpoint with pre-copying mechanism hasn't been
> enabled in Xen yet as the necessary code is all there.
>
> Cheers,
> Mike
>
> diff -r dca3b5e459e3 tools/python/xen/xend/XendDomain.py
> --- a/tools/python/xen/xend/XendDomain.py       Wed Sep 17 15:46:05 2008 +0100
> +++ b/tools/python/xen/xend/XendDomain.py       Fri Nov 14 13:28:39 2008 -0500
> @@ -1333,7 +1333,8 @@
>                 oflags |= os.O_LARGEFILE
>             fd = os.open(dst, oflags)
>             try:
> -                XendCheckpoint.save(fd, dominfo, False, False, dst,
> +                live = True
> +                XendCheckpoint.save(fd, dominfo, False, live, dst,
>                                     checkpoint=checkpoint)
>             except Exception, e:
>                 os.close(fd)

_______________________________________________
Xen-research mailing list
Xen-research@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-research

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