From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37142) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ul0Nc-0005VO-AV for qemu-devel@nongnu.org; Fri, 07 Jun 2013 13:23:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ul0Nb-0006GY-Ek for qemu-devel@nongnu.org; Fri, 07 Jun 2013 13:23:12 -0400 Received: from mail-pb0-x22c.google.com ([2607:f8b0:400e:c01::22c]:63135) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ul0Nb-0006GP-8R for qemu-devel@nongnu.org; Fri, 07 Jun 2013 13:23:11 -0400 Received: by mail-pb0-f44.google.com with SMTP id uo1so186004pbc.3 for ; Fri, 07 Jun 2013 10:23:10 -0700 (PDT) Message-ID: <51B216F6.4040709@gmail.com> Date: Sat, 08 Jun 2013 01:23:02 +0800 From: Liu Yuan MIME-Version: 1.0 References: <1370519849-10620-1-git-send-email-namei.unix@gmail.com> <1370519849-10620-3-git-send-email-namei.unix@gmail.com> <20130606124629.GE2586@dhcp-200-207.str.redhat.com> <51B08A25.30604@gmail.com> <20130607073118.GA3658@dhcp-200-207.str.redhat.com> <51B1E4C7.5070902@gmail.com> <20130607152246.GH3658@dhcp-200-207.str.redhat.com> <51B206E2.6020007@gmail.com> <20130607164826.GI3658@dhcp-200-207.str.redhat.com> In-Reply-To: <20130607164826.GI3658@dhcp-200-207.str.redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/2] sheepdog: support 'qemu-img snapshot -a' List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: Stefan Hajnoczi , sheepdog@lists.wpkg.org, qemu-devel@nongnu.org, MORITA Kazutaka On 06/08/2013 12:48 AM, Kevin Wolf wrote: > Hm, yes, I was confused. :-) > > Anyway, the options stay the same: Either C1 must somehow inherit the VM > state from A on the Sheepdog level, or we must make sure to get this > order: > > 1. Switch to (read-only) snapshot A > 2. Load the VM state > 3. Create (writable) snapshot C1 and switch to it > > This is a different order as required for qcow2 (where C1 would inherit > the VM state from A, so our current first 1, then 3, then 2 works), but > if we can't fix it on the Sheepdog side, we'll have to touch the core > code of qemu. I don't like much to touch the block.c code for it, but if > it's required to fix a bug, let's just do it. Hmm, I found actually we can inherit A's vdi_id from C1. I've sent v3 and I think this version will fix the possible bug you pointed out and do loadvm the way core code assumes. Thanks, Yuan