From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33206) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZV2Xc-0007LO-Ks for qemu-devel@nongnu.org; Thu, 27 Aug 2015 15:08:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZV2XX-0004KI-Hh for qemu-devel@nongnu.org; Thu, 27 Aug 2015 15:08:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58893) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZV2XX-0004J0-CC for qemu-devel@nongnu.org; Thu, 27 Aug 2015 15:08:47 -0400 Date: Thu, 27 Aug 2015 15:08:43 -0400 From: Jeff Cody Message-ID: <20150827190843.GM11016@localhost.localdomain> References: <56530C98-D6B3-417E-BB58-E29412283BF1@gmail.com> <20150827134943.GS24486@redhat.com> <37557843-A1BA-4822-9933-B0B8AD588C90@gmail.com> <55DF1884.2030608@redhat.com> <20150827144253.GX24486@redhat.com> <20150827154057.GE2669@localhost.localdomain> <068B4976-968C-45A3-9219-77FB600BC257@gmail.com> <20150827160217.GA24486@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150827160217.GA24486@redhat.com> Subject: Re: [Qemu-devel] Should we auto-generate IDs? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: Kevin Wolf , jsnow@redhat.com, Markus Armbruster , qemu-devel qemu-devel , Programmingkid , Paolo Bonzini , Andreas =?iso-8859-1?Q?F=E4rber?= On Thu, Aug 27, 2015 at 05:02:17PM +0100, Daniel P. Berrange wrote: > > Just to be clear - libvirt will *never* use an auto-generated device > IDs feature. It is way more complicated to let QEMU assign device IDs > and then auto-detect them from some 'info device-list' output, than > to just specify IDs upfront at device/object creation time which > it already does[1]. There is simply no benefit to auto-generating device > IDs for a mgmt app like libvirt, and plenty of downside. Auto-generated > IDs will only be of interest to humans talking to the monitor directly > without a mgmt app involved. > > Regards, > Daniel > > [1] we don't provide IDs for qcow2 image backing file chain, but that's > part of a bigger story that's being dealt with in this area. This is the part that interests me the most :) Do you think in dealing with image backing file chains, libvirt would ever make use of QEMU auto-generated node-names (either in the current feature set, or with future features)? I'm not sure if your above statement is specific to device ID, or extends to node-names as well. Thanks, Jeff