All of lore.kernel.org
 help / color / mirror / Atom feed
From: Killian De Volder <killian.de.volder@scarlet.be>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: xm save (but don't destroy)
Date: Tue, 12 Oct 2010 08:32:32 +0200	[thread overview]
Message-ID: <4CB40100.4050405@scarlet.be> (raw)

  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

             reply	other threads:[~2010-10-12  6:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12  6:32 Killian De Volder [this message]
2010-10-12  6:42 ` xm save (but don't destroy) Keir Fraser
2010-10-12 17:40   ` Killian De Volder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CB40100.4050405@scarlet.be \
    --to=killian.de.volder@scarlet.be \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.