From mboxrd@z Thu Jan 1 00:00:00 1970 From: Killian De Volder Subject: Re: xm save (but don't destroy) Date: Tue, 12 Oct 2010 19:40:11 +0200 Message-ID: <4CB49D7B.7040903@scarlet.be> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.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" > 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 >