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

To: Killian De Volder <killian.de.volder@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm save (but don't destroy)
From: Keir Fraser <keir@xxxxxxx>
Date: Tue, 12 Oct 2010 07:42:31 +0100
Delivery-date: Mon, 11 Oct 2010 23:43:29 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:user-agent:date :subject:from:to:message-id:thread-topic:thread-index:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=hMK4/xCftVpCTbepOTJa926nNx68SVUOxaGkSA0h1DE=; b=vKwjojgD2CFgkPc7G4GbbX1PMPrvKi75lWqljqXjJKWSeUIvRc3Gp74em/sVIuFNNr TEu84xDHzRCaNZyf4EQ1cctu6+MfO5YhzP4iB+4D6P/GuQg0mwQ9dDnyIzyCxhydhZVi H9jCpvYDq4Y+A9LbClNiWz7FdH5hDLXwbnR4I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=vfdvNCTL0PyrXYcA1w+gK5f/CMrxqTBlriQNuHXhrHj4c3S9TVSopk+uYMQQ4TqoA6 IXX1jiO1QxIi56GGdhweoXrcWJJfUdeTVCRTZ2708UMscf4o0olChUQWvUAeFp86lbXu vfq0c4U0GATzDlMCPkCrYV1GXhMEF3n6Ppk1c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CB40100.4050405@xxxxxxxxxx>
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
Thread-index: Actp2KTd1Wuf/Swaf0+cN1BeURB+pQ==
Thread-topic: [Xen-devel] xm save (but don't destroy)
User-agent: Microsoft-Entourage/
On 12/10/2010 07:32, "Killian De Volder" <killian.de.volder@xxxxxxxxxx>

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

xm save -c

 -- Keir

> Greeting and thanks in advance,
> Killian
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

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