From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40101) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5YI6-00007n-FM for qemu-devel@nongnu.org; Thu, 18 Jun 2015 07:47:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5YI5-0008V7-7T for qemu-devel@nongnu.org; Thu, 18 Jun 2015 07:47:30 -0400 Date: Thu, 18 Jun 2015 13:47:20 +0200 From: Kevin Wolf Message-ID: <20150618114720.GE4270@noname.redhat.com> References: <20150616085102.GA22306@perseus.local> <20150618104535.GD4270@noname.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v7 00/11] Support streaming to an intermediate layer List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alberto Garcia Cc: qemu-block@nongnu.org, armbru@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com, Max Reitz Am 18.06.2015 um 13:41 hat Alberto Garcia geschrieben: > On Thu 18 Jun 2015 12:45:35 PM CEST, Kevin Wolf wrote: > > > I believe our conclusion from an earlier version of the series was > > that we need QAPI introspection so that libvirt can detect the > > presence of the feature. > > The initial version of this series had an extra 'top' parameter to > decide what image to stream data into. That's what prompted the > discussion: > > https://lists.gnu.org/archive/html/qemu-devel/2015-02/msg04182.html > > That was later removed when we agreed that we could just reuse the > 'device' parameter to refer to either a device or a node name. > > I don't think that introspection support would make a difference in this > case, or am I missing anything? Hm, yes, probably not. But how would libvirt detect the feature then? Kevin