Re: [Xen-devel] xm save (but don't destroy)

[Killian De Volder <killian.de.volder@xxxxxxxxxx>]

 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@xxxxxxxxxx>
> 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@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel