All of lore.kernel.org
 help / color / mirror / Atom feed
* xm save (but don't destroy)
@ 2010-10-12  6:32 Killian De Volder
  2010-10-12  6:42 ` Keir Fraser
  0 siblings, 1 reply; 3+ messages in thread
From: Killian De Volder @ 2010-10-12  6:32 UTC (permalink / raw)
  To: xen-devel@lists.xensource.com

  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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: xm save (but don't destroy)
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Keir Fraser @ 2010-10-12  6:42 UTC (permalink / raw)
  To: Killian De Volder, xen-devel@lists.xensource.com

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: xm save (but don't destroy)
  2010-10-12  6:42 ` Keir Fraser
@ 2010-10-12 17:40   ` Killian De Volder
  0 siblings, 0 replies; 3+ messages in thread
From: Killian De Volder @ 2010-10-12 17:40 UTC (permalink / raw)
  To: xen-devel

  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
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-10-12 17:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.