[libvirt] [PATCH v2] qemu: Allow UEFI paths to be specified at compile time

[Gerd Hoffmann]

On Mi, 2014-12-03 at 12:43 +0000, Daniel P. Berrange wrote:
> On Wed, Dec 03, 2014 at 01:35:18PM +0100, Gerd Hoffmann wrote:
> >   Hi,
> > 
> > > Hmm, so it occurrs to me that this is really about detecting what
> > > BIOS capabilities QEMU is able to support.
> > 
> > IMHO this isn't a property of qemu, but a property of the firmware.
> > 
> > Thats why I think the firmware packages should include some config file
> > with the meta data.
> 
> It feels related to QEMU because you need to have info about whether
> to use -bios or -pflash,

That again depends on the firmware (whenever it wants store state in
flash or not) not qemu.

> and info about the format raw vs qcow2

Again depends on the firmware.  -pflash accepts any blockdev, so we can
use qcow2 there, which could be useful for the largely empty vars file,
especially for arm where it is 64M in size.

> and
> whether the firmware is compatible with the particular system emulator
> arch.

That needs to be in the firmware metadata anyway, qemu wouldn't
magically know this either.

> The location of the firmware and/or firmware config files can vary
> depending on what $PREFIX QEMU was installed in.

I don't want that.  Well, the images itself should be
in /usr/share/$package.  But for the firmware config file I want a fixed
location, not something depending on the qemu $prefix.

> I don't think that
> external apps should have to care about where the firmware or the
> firmware config files are installed - that's QEMU's build time knowledge.

Firmware is *not* built together with qemu.

cheers,
  Gerd