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


[Xen-devel] Fwd: Xen Saving VM

To: xen-devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-research list <xen-research@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Fwd: Xen Saving VM
From: Omer Khalid <Omer.Khalid@xxxxxxx>
Date: Mon, 11 May 2009 10:42:26 +0200
Delivery-date: Mon, 11 May 2009 01:42:53 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=PcbSb7AI00MN2hYbOPoTfMsy8mUgbInzvriot1XK1uM=; b=vMuk86wQrrSencHNrRwNGUpYX+tGgOcsT2Gc8loWj8yAIlvl2b1ayDpXtJU2BAvMMm wNeg/ds7agGjkwt4thzsAoGc6AuAi0lsDJRvwZgNDXp4KR2WHQkQ34Py5Ozh+4fe0cib KMK/7wOLc1Cz/Hj5UH5uOD61B35c8ZX8mVGgo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=RfHgOF5kzkslK3MWYS6sVBTvrVL18Hg2dbrdMY1/PLcsuhPAmOvBCOt2b7je7BXrpx 73vdsTkfoW48wVJFQhM+qe4Yng8GH1KTReE/rhflxzi0FwPdOnbdkJsvgY+x4Ufxv94T 351qfrcF4fw54QxqhhN49SDIaDO0F+tmiX8+k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <77e5896b0905020553i3c371bd5g27b52f934ec29a0d@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <77e5896b0905020553i3c371bd5g27b52f934ec29a0d@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


I am trying to understand Xen's save VM state works.

I have use case where I am running 3 VM's on a 4-core/8GB server with 1core/2GB per VM. Each of the VM runs an HPC application, and most of the time 1.5GB memory is allocated to the application running in the VM.

Now I am trying to do is to pause VM-1 and VM-2. Save their respective states. Reduce their memory and cap CPU to lowest possible value; then to alloacate the taken resource from VM-1 and VM-2 to VM-3 for X amount of time. Once the application in VM-3 is finished, then I reduce it's CPU/Memory to pre-start stage and re-allocate 1CPU/2GB again to VM-1 and VM-2

My question is; would the application in VM-1 or VM-2 will be able to start executing from the last saved point. Is there a way in Xen to check-point this?


CERN, Engineering Department,
CH-1211 Geneva 23, Switzerland
Email:  Omer.Khalid@xxxxxxx

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>