Re: [libvirt] [PATCH 1/3] firmware: include arch and features in firmware file list
On Wed, Oct 19, 2016 at 02:52:20PM +0100, Richard W.M. Jones wrote:
On Wed, Oct 19, 2016 at 02:22:19PM +0100, Daniel P. Berrange wrote:
> Oh, but that's outside scope of libvirt then - we're not looking to
> expose APIs to help people run QEMU directly.
Well, yes, but that doesn't mean we cannot cooperate. These wouldn't
be libvirt APIs, just a standard configuration file somewhere listing
the UEFI binaries. Or perhaps more simply, a more sensible naming of
UEFI binaries so they're always in a standard location with standard
names.
I think this would be something QEMU has to define. Unfortunately I
don't think simple filenaming conventions will work for UEFI, since
depending on which QEMU features you turn on you need to pick
different images - indeed we already have every distro using different
path names for UEFI, which is why libvirt already has this config
parameter :-( QEMU could define some file format with mapping info,
that listed which UEFI binaries are valid for what QEMU features.
QEMU could ship a default file, and OS distro vendors could as/if
needed
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|