From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43794) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WztIl-0008MA-Fu for qemu-devel@nongnu.org; Wed, 25 Jun 2014 15:56:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WztIf-0007UN-Js for qemu-devel@nongnu.org; Wed, 25 Jun 2014 15:56:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36218) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WztIf-0007UD-Bi for qemu-devel@nongnu.org; Wed, 25 Jun 2014 15:56:09 -0400 Date: Wed, 25 Jun 2014 15:56:05 -0400 From: Jeff Cody Message-ID: <20140625195605.GC7730@localhost.localdomain> References: <53AB2879.8030100@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53AB2879.8030100@redhat.com> Subject: Re: [Qemu-devel] [PATCH v7 for 2.1 4/4] block: add QAPI command to allow live backing file change List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: kwolf@redhat.com, benoit.canet@irqsave.net, pkrempa@redhat.com, famz@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com On Wed, Jun 25, 2014 at 01:52:25PM -0600, Eric Blake wrote: > On 06/25/2014 01:40 PM, Jeff Cody wrote: > > This allows a user to make a live change to the backing file recorded in > > an open image. > > > > The image file to modify can be specified 2 ways: > > > > 1) image filename > > 2) image node-name > > > > Note: this does not cause the backing file itself to be reopened; it > > merely changes the backing filename in the image file structure, and > > in internal BDS structures. > > > > It is the responsibility of the user to pass a filename string that > > can be resolved when the image chain is reopened, and the filename > > string is not validated. > > > > A good analogy for this command is that it is a live version of > > 'qemu-img rebase -u', with respect to changing the backing file string. > > For 2.1, did we want to limit this command to only affecting the active > layer (and failing if it was attempted on a backing file), in order to > simplify dealing with op-blocker work? Having the command exist, even > if it is limited in nature, is all the more libvirt wants right now; and > it's easier to relax a constraint in a future release than it is to > release something now and have to keep it working even after we rework > op-blockers in the future. > I left this as-is, because the blocker issue needs to be addressed somehow for 2.1. And once we know in what manner, I'll just update this series to use that methodology (if necessary). Unless Stefan or Kevin would prefer that I change this to only operate on the active layer, of course. > > > > Reviewed-by: Eric Blake > > Signed-off-by: Jeff Cody > > I'm still okay with this patch as-is, if we are okay with the ability to > rename the backing file of a non-active node. > > -- > Eric Blake eblake redhat com +1-919-301-3266 > Libvirt virtualization library http://libvirt.org >