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] xm save (but don't destroy)

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] xm save (but don't destroy)
From: Killian De Volder <killian.de.volder@xxxxxxxxxx>
Date: Tue, 12 Oct 2010 08:32:32 +0200
Delivery-date: Mon, 11 Oct 2010 23:33:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101010 Thunderbird/3.1.4
 Hello all,

I'm sure this has been asked before but I couldn't find a reference:
I desire to pauze/save the state of dom, backup/snapshot the disk and then 
unpauze the domain.

This can be done with xm save, but this destroy the machine, effectively 
doubling the required time to snapshot the machine.
(As you first have to save it to disk .... and then load it again ... With 
machine with a couple gigabyes of RAM this can start to take a while.)

I did see xend/XendCheckpoint.py has some code in it that decides if it will destroy or 
resume the machine ... This makes me thing that adding the option "leave 
pauzed" isn't to hard ?

Greeting and thanks in advance,

Xen-devel mailing list

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