From mboxrd@z Thu Jan  1 00:00:00 1970
From: Killian De Volder <killian.de.volder@scarlet.be>
Subject: xm save (but don't destroy)
Date: Tue, 12 Oct 2010 08:32:32 +0200
Message-ID: <4CB40100.4050405@scarlet.be>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

  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,
Killian