From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42378) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f5rnB-0006vj-Qt for qemu-devel@nongnu.org; Tue, 10 Apr 2018 07:50:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f5rn7-0008Gk-Uh for qemu-devel@nongnu.org; Tue, 10 Apr 2018 07:50:29 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:39256 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f5rn7-0008GZ-JL for qemu-devel@nongnu.org; Tue, 10 Apr 2018 07:50:25 -0400 Date: Tue, 10 Apr 2018 12:50:18 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Message-ID: <20180410115018.GS5155@redhat.com> Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= References: <20180407000117.25640-1-lersek@redhat.com> <20180409084940.GE18283@redhat.com> <3381bdf1-62ea-9da7-c654-032c0c11fb4e@redhat.com> <20180410091832.GG5155@redhat.com> <20180410113444.GR5155@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [qemu RFC] qapi: add "firmware.json" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: qemu-devel@nongnu.org, libvir-list@redhat.com, Alexander Graf , Ard Biesheuvel , David Gibson , Eric Blake , Gary Ching-Pang Lin , Gerd Hoffmann , Kashyap Chamarthy , Markus Armbruster , Michael Roth , Michal Privoznik , Peter Krempa , Peter Maydell , Thomas Huth On Tue, Apr 10, 2018 at 01:44:13PM +0200, Laszlo Ersek wrote: > On 04/10/18 13:34, Daniel P. Berrang=C3=A9 wrote: > > On Tue, Apr 10, 2018 at 01:27:18PM +0200, Laszlo Ersek wrote: > >=20 > >> Please go through the rest of the emails in this thread, and advise: > >> - if the firmware descriptor schema may perhaps live in the libvirt = tree, > >> - accordingly, if the schema could be expressed as an XSD (and firmw= are > >> packages should provide the descriptor documents as XMLs) > >> - if you agree that the descriptor document can uniquely reference > >> mapping methods implemented in libvirtd by simple enum constants (wi= th > >> necessary parameters provided). > >=20 > > No to all three. This is the responsibility of QEMU to define, becaus= e > > this information is relevant to anything managing QEMU not just libvi= rt. >=20 > In that case, how do you suggest we describe the QEMU command line > options that are (a) necessary, (b) "discoverable" to the management > application? Should we provide verbatim command line fragments (option > templates)? Is this feature meant to replace the cmdline generation > logic that already exists in libvirtd? Each part of the schema should have docs describing what CLI args it corresponds to. eg document that when device=3Dmemory, corresponds to -bios, that device=3Dflash, corresponds to -drive if=3Dpflash, etc We've not trying to replace the cmdline generator in libvirt. We just want to know that when we see a particular field present in the schema, that it corresponds to a particular cli arg. Regards, Daniel --=20 |: https://berrange.com -o- https://www.flickr.com/photos/dberran= ge :| |: https://libvirt.org -o- https://fstop138.berrange.c= om :| |: https://entangle-photo.org -o- https://www.instagram.com/dberran= ge :|