On 10 April 2018 at 12:34, Daniel P. Berrangé <berra...@redhat.com> wrote: > On Tue, Apr 10, 2018 at 01:27:18PM +0200, Laszlo Ersek wrote: > >> 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 firmware >> 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 (with >> necessary parameters provided). > > No to all three. This is the responsibility of QEMU to define, because > this information is relevant to anything managing QEMU not just libvirt.
(Please consider this as more of a grenade lobbed into the conversation rather than a carefully thought out proposal...) My inclination is to say that it's not really the responsibility of QEMU to define either -- we provide emulated models of hardware, and it's up to the user or the management layer or the provider of the firmware to specify what guest code they want to run and how it needs to run on that emulated hardware... Where the QEMU upstream itself is providing firmware blobs (in tarballs etc) it's probably our job to specify how they work, but if the firmware is compiled and provided by the distro (as eg happens for Arm UEFI blobs at the moment) then I don't see how upstream QEMU can reliably define how that firmware needs to be loaded. thanks -- PMM