From mboxrd@z Thu Jan 1 00:00:00 1970 From: tgh Subject: Re: how to make checkpoint for a PV vm , while maintain it running ? Date: Thu, 22 Nov 2007 16:21:24 +0800 Message-ID: <47453C04.2090100@sina.com.cn> References: <34958.46503.qm@web45614.mail.sp1.yahoo.com> <47443172.4050306@sina.com.cn> <20071122015610.GB6065@xanadu.kublai.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20071122015610.GB6065@xanadu.kublai.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: wwwwww4187@sina.com.cn, xen-users@lists.xensource.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org hi Thank your for your advise that is to say , xen-3.1.0 does not support checkpoint while maintaining=20 PV vm running ,is it ?or maybe ,there are something I have missed=20 beforing checkpointing on xen-3.1.0, for the node is shared by some=20 fellows at present, i guess I will try xen-3.1.1 later, but how to deal=20 with it on xen-3.1.0 anyway ? or it could not on xen-3.1.0? Thanks Brendan Cully =E5=86=99=E9=81=93: > On Wednesday, 21 November 2007 at 21:24, tgh wrote: > =20 >> hi >> I have tried to make checkpoint for a PV vm with"xm save -c dom1 =20 >> /tmp/dom1 "in xen-3.1.0,the ckeckpoint file could be used to restore t= he =20 >> vm, but the vm do not continue to run ,after "xm save -c dom1 =20 >> /tmp/dom1",the vm could not be accessed through console ,could not be = =20 >> shutdown using"xm shutdown dom1" and could not be pinged from dom0, b= ut =20 >> "xm destroy dom1" could work, >> should some configures be set before "xm save -c ",or what should = i =20 >> do to make a vm checkpoint, while maintain the checkpointed vm running= ? >> =20 > > I've just tried this on Xen 3.1.2 and it seems to work fine. So I'd sug= gest first > upgrading Xen, and then if you still have problems, build xen with debu= g=3Dy verbose=3Dy > and see if anything turns up in xend.log or /var/log/daemon or the gues= t console. > > > =20