From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53679) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUxk5-0007o1-2Z for qemu-devel@nongnu.org; Thu, 27 Aug 2015 10:01:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZUxjz-0006xK-AF for qemu-devel@nongnu.org; Thu, 27 Aug 2015 10:01:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36311) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUxjy-0006x2-R6 for qemu-devel@nongnu.org; Thu, 27 Aug 2015 10:01:19 -0400 References: <87fv36j9j6.fsf@blackfin.pond.sub.org> <20150826172550.GJ11016@localhost.localdomain> <20150826180815.GK11016@localhost.localdomain> <20150826220151.GA2669@localhost.localdomain> <2CB0CE30-A638-4933-A1D6-F65CA4910E61@gmail.com> <20150827123234.GB2669@localhost.localdomain> <55DF09DB.2000406@redhat.com> <221424A1-B3AA-4746-BAF3-BEBCC1CA73DC@gmail.com> <20150827135120.GT24486@redhat.com> From: Eric Blake Message-ID: <55DF1828.4000904@redhat.com> Date: Thu, 27 Aug 2015 08:01:12 -0600 MIME-Version: 1.0 In-Reply-To: <20150827135120.GT24486@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cHde1h05N718lfumQb31LCOnuGl6bwuH1" 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" , Programmingkid Cc: Kevin Wolf , Jeff Cody , Markus Armbruster , qemu-devel qemu-devel , Paolo Bonzini , jsnow@redhat.com, =?UTF-8?Q?Andreas_F=c3=a4rber?= This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --cHde1h05N718lfumQb31LCOnuGl6bwuH1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 08/27/2015 07:51 AM, Daniel P. Berrange wrote: > On Thu, Aug 27, 2015 at 09:39:10AM -0400, Programmingkid wrote: >> >>> Better still might be fixing things to where we add a global command >>> line option that outright fails any attempt to create an unnamed obje= ct. >>> The option would be off by default for back-compat. But management >>> apps like libvirt can turn it on once they are prepared to name every= >>> object they create (which in turn may imply fixing any remaining >>> interfaces that cannot name an object to add in that ability for >>> management to pass in a name). Then there would be no unnamed object= s, >>> no ambiguity, and no need to generate names. >> >> I do agree with giving every device an ID, but I don't think failing i= f the user >> forgets to give one is necessary. If libvirt doesn't give devices and = ID, it >> would probably benefit from having QEMU do it for libvirt. No, you're misunderstanding our argument. The moment there is more than one device with an auto-assigned name is the moment that management doesn't know which device got which name, so it's better for management to pick a name in the first place. >=20 > Libvirt always gives an explicit ID. Except it doesn't, yet. Libvirt still needs to be taught to name all node devices (and I'm slowly trying to work on patches towards that goal)= =2E > It is impossible to rely on QEMU > assigning IDs, because there is no reliable way to identify what ID > QEMU assigned to each device after the fact. Other management apps > would have the same problem, so auto-generated IDs are pretty useless > in that respect. It's not to say that auto-generated names would be useless when running qemu manually from the command line, but I agree that management probably can't safely rely on auto-generated names, and therefore solving the issue of auto-generating names is less important. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --cHde1h05N718lfumQb31LCOnuGl6bwuH1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJV3xgoAAoJEKeha0olJ0NqWVcH/RMPFTun7AJpeeRxeyaDdRBD +QK2hacCeu9z5x/ZYvH1i6UlORWwW+HLo+1dzYbSwfqeKZEGCiFl0wVjlpde9ctu ayxkGjqPQQEIvll9/9Gk539CQXaLEA7q8OY5bTlQOIiLfW1UBlJie+5iqDFAoIQj 1ZgIZognfSP4dgO4n9q18gmqI7ym/ayQz9uQyOMq3GMNu8q8nN3HvEdVTg0VU438 ghKdTBX+gRBoR5rueCKFk/AwTxCJkznrDuOYOUKPuSH3MojKvfE57ZvZ65Nwfbt0 3I+jJap6kY3LuT9kosLgqWyyyXJGJIbXdGTznUPmRXGW9y0gUy6ysiywe+zibG8= =NfLo -----END PGP SIGNATURE----- --cHde1h05N718lfumQb31LCOnuGl6bwuH1--