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] how to make checkpoint for a PV vm , while maintain it

To: wwwwww4187@xxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] how to make checkpoint for a PV vm , while maintain it running ?
From: tgh <wwwwww4187@xxxxxxxxxxx>
Date: Thu, 22 Nov 2007 16:21:24 +0800
Delivery-date: Thu, 22 Nov 2007 00:22:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071122015610.GB6065@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/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: <34958.46503.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <47443172.4050306@xxxxxxxxxxx> <20071122015610.GB6065@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20060909)
Thank your for your advise
that is to say , xen-3.1.0 does not support checkpoint while maintaining PV vm running ,is it ?or maybe ,there are something I have missed beforing checkpointing on xen-3.1.0, for the node is shared by some fellows at present, i guess I will try xen-3.1.1 later, but how to deal with it on xen-3.1.0 anyway ? or it could not on xen-3.1.0?


Brendan Cully 写道:
On Wednesday, 21 November 2007 at 21:24, tgh wrote:
I have tried to make checkpoint for a PV vm with"xm save -c dom1 /tmp/dom1 "in xen-3.1.0,the ckeckpoint file could be used to restore the vm, but the vm do not continue to run ,after "xm save -c dom1 /tmp/dom1",the vm could not be accessed through console ,could not be shutdown using"xm shutdown dom1" and could not be pinged from dom0, but "xm destroy dom1" could work, should some configures be set before "xm save -c ",or what should i do to make a vm checkpoint, while maintain the checkpointed vm running?

I've just tried this on Xen 3.1.2 and it seems to work fine. So I'd suggest 
upgrading Xen, and then if you still have problems, build xen with debug=y 
and see if anything turns up in xend.log or /var/log/daemon or the guest 

Xen-devel mailing list