From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KNpPf-0006wG-Jm
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 09:38:51 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KNpPe-0006va-5c
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 09:38:51 -0400
Received: from [199.232.76.173] (port=42203 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KNpPd-0006vV-VA
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 09:38:49 -0400
Received: from wr-out-0506.google.com ([64.233.184.235]:53192)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1KNpPd-0000WD-JZ
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 09:38:49 -0400
Received: by wr-out-0506.google.com with SMTP id c46so4430123wra.18
	for <qemu-devel@nongnu.org>; Tue, 29 Jul 2008 06:38:48 -0700 (PDT)
Message-ID: <488F1D41.8010107@codemonkey.ws>
Date: Tue, 29 Jul 2008 08:38:09 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] qcow3 - arbitrary metadata
References: <a38baa500807281256s7aa6c69em344c655145956b24@mail.gmail.com>	<488E2752.7030008@codemonkey.ws>	<20080729014939.GA27149@shareable.org>	<488E8AE8.2060602@codemonkey.ws>
	<20080729064412.GA32582@shareable.org>
In-Reply-To: <20080729064412.GA32582@shareable.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Jamie Lokier wrote:
> Anthony Liguori wrote:
>   
>>> Yeah, I have the opposite problem - too much in the same file :-)
>>>
>>> I want to be able to savevm, but some of my VMs don't have any qcow2
>>> images (because I don't trust them for mission-critical VMs since
>>> recent discussion,
>>>       
>> How do you snapshot the disk images?
>>     
>
> Does savevm snapshot the disk images too?

Yes.

>   I thought it was just the
> machine state.  Does that mean non-qcow2 disks (e.g. raw files) are
> not snapshotted but qcow2 ones are, in the same VM?
>   

Raw files cannot be snapshotted.

> It's actually just the machine state I want to save.  I want to use
> savevm to save the state of the VM before quitting, and loadvm to
> restart.  Like suspend-to-RAM, but doesn't require the guest to
> cooperate.  (Does suspend work anyway?)
>   

If you do that, you risk having your disk in an improper state.  If 
there are any changes to the disk after you do your savevm, they will 
not be present after you loadvm.  This could cause very subtle data 
corruption within your file system.

Regards,

Anthony Liguori