From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48358) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZcrYX-0004gn-KR for qemu-devel@nongnu.org; Fri, 18 Sep 2015 05:02:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZcrYW-0007yD-VM for qemu-devel@nongnu.org; Fri, 18 Sep 2015 05:02:09 -0400 Date: Fri, 18 Sep 2015 11:02:03 +0200 From: Kevin Wolf Message-ID: <20150918090203.GA4320@noname.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] internal snapshots with sheepdog List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vasiliy Tolstov Cc: mitake.hitoshi@lab.ntt.co.jp, namei.unix@gmail.com, sheepdog@lists.wpkg.org, qemu-devel , qemu-block@nongnu.org Am 11.09.2015 um 17:49 hat Vasiliy Tolstov geschrieben: > Hi! qcow2 have abilit to store vm state inside qcow2 file in space > that not allocated to guest, but if i want to store vm state inside > sheepdog storage with raw image what is the preferred place to store > memory data? > I simply can create additional vdi equa to memory size of the guest > and save memory to this file... Doesn't sheepdog already support storing snapshots in the same image? I thought it would just work; at least, there's some code there for it. Kevin