From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46537) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uorxr-0000SP-3m for qemu-devel@nongnu.org; Tue, 18 Jun 2013 05:12:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uorxo-0003hl-GB for qemu-devel@nongnu.org; Tue, 18 Jun 2013 05:12:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38915) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uorxo-0003hh-8i for qemu-devel@nongnu.org; Tue, 18 Jun 2013 05:12:32 -0400 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r5I9CVkF007990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 18 Jun 2013 05:12:31 -0400 Date: Tue, 18 Jun 2013 17:12:31 +0800 From: Fam Zheng Message-ID: <20130618091231.GA13053@localhost.nay.redhat.com> References: <20130617093241.GA22609@localhost.nay.redhat.com> <51BEDCB9.5090905@redhat.com> <20130617135253.GB3994@dhcp-200-207.str.redhat.com> <51BF16B8.6040801@redhat.com> <20130617142605.GD3994@dhcp-200-207.str.redhat.com> <51BF213F.60601@redhat.com> <20130617151238.GF3994@dhcp-200-207.str.redhat.com> <20130618035854.GA17533@localhost.nay.redhat.com> <871u7zx6u3.fsf@blackfin.pond.sub.org> <51C01CEF.4070907@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51C01CEF.4070907@redhat.com> Subject: Re: [Qemu-devel] [PATCH] block: add 'backing' option to drive_add List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Kevin Wolf , Markus Armbruster , stefanha@redhat.com, qemu-devel@nongnu.org On Tue, 06/18 10:40, Paolo Bonzini wrote: > Il 18/06/2013 08:37, Markus Armbruster ha scritto: > > > If not, can we try to detect such case on opening > > Gee, what a nice swamp you found there! > > It is a huge swamp indeed. > > Since we stop all block jobs on media change already, what about just > adding a command "block-job-attach" or something like that which exposes > the target of the job as a blockdev (presumably so that you can then add > it to the NBD server)? > In fact block job target BDS is already created when job started, so it's rather about finding a way to "query" the target BDS name, or get it as command return value, than attach a blockdev. Once we have the device name, we can add it to the NBD server. -- Fam