From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LPZ2j-0003nG-OD for qemu-devel@nongnu.org; Wed, 21 Jan 2009 04:06:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LPZ2i-0003n4-6O for qemu-devel@nongnu.org; Wed, 21 Jan 2009 04:06:37 -0500 Received: from [199.232.76.173] (port=47621 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPZ2i-0003n1-2t for qemu-devel@nongnu.org; Wed, 21 Jan 2009 04:06:36 -0500 Received: from mx2.suse.de ([195.135.220.15]:51627) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LPZ2h-0001If-Mj for qemu-devel@nongnu.org; Wed, 21 Jan 2009 04:06:35 -0500 Received: from Relay1.suse.de (relay-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.suse.de (Postfix) with ESMTP id 2D1214772F for ; Wed, 21 Jan 2009 10:06:32 +0100 (CET) Message-ID: <4976E704.7020607@suse.de> Date: Wed, 21 Jan 2009 10:12:36 +0100 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] Combining "loadvm" and "-snapshot" References: <18806.25890.35889.274762@amuro.CS.Berkeley.EDU> In-Reply-To: <18806.25890.35889.274762@amuro.CS.Berkeley.EDU> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Stephen McCamant schrieb: > I've tried implementing an alternate approach that makes "loadvm" work > under "-snapshot" by finding and loading the VM state from the backing > image, if a snapshot with that name isn't found in the scratch image. > In some preliminary testing, this seems to do what I want; you can > also make new snapshots with savevm that live only in the scratch > image (and so go away at the end of the session). I think, this is the point where your approach will break. A snapshot in the scratch image is still based on a snapshot in the backing image. So on loading the scratch snapshot you would also need to load the snapshot for the backing file. However, you don't know which one because qcow2 can't save a snapshot name for the backing file. Kevin