From: Killian De Volder <killian.de.volder@scarlet.be>
To: xen-devel@lists.xensource.com
Subject: Re: xm save (but don't destroy)
Date: Tue, 12 Oct 2010 19:40:11 +0200 [thread overview]
Message-ID: <4CB49D7B.7040903@scarlet.be> (raw)
In-Reply-To: <C8D9C1E7.25A5A%keir@xen.org>
But that won't leave the VM in pauzed state ...
As a result you cannot backup the disks ...
But I have been thinking ...
Would
xm pauze
backup/snapshot disk
xen save -c
work ?
Or will this introduce unexpected problems ?
Greetings,
Killian
> On 12/10/2010 07:32, "Killian De Volder"<killian.de.volder@scarlet.be>
> wrote:
>
>> 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@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2010-10-12 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 6:32 xm save (but don't destroy) Killian De Volder
2010-10-12 6:42 ` Keir Fraser
2010-10-12 17:40 ` Killian De Volder [this message]
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=4CB49D7B.7040903@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.