Re: [libvirt] [PATCH 2/3] conf: add support for choosing firmware type

2016-10-19 Thread Daniel P. Berrange
On Wed, Oct 19, 2016 at 01:09:56PM +0100, Richard W.M. Jones wrote: > On Mon, Oct 03, 2016 at 04:49:48PM +0100, Daniel P. Berrange wrote: > > Currently if you want to enable UEFI firmware for a guest > > you need to know about the hypervisor platform specific > > firmware path. This does not even

Re: [libvirt] [PATCH 2/3] conf: add support for choosing firmware type

2016-10-19 Thread Richard W.M. Jones
On Mon, Oct 03, 2016 at 04:49:48PM +0100, Daniel P. Berrange wrote: > Currently if you want to enable UEFI firmware for a guest > you need to know about the hypervisor platform specific > firmware path. This does not even work for all platforms, > as hypervisors like VMWare don't expose UEFI as a

Re: [libvirt] [PATCH 2/3] conf: add support for choosing firmware type

2016-10-11 Thread John Ferlan
On 10/03/2016 11:49 AM, Daniel P. Berrange wrote: > Currently if you want to enable UEFI firmware for a guest > you need to know about the hypervisor platform specific > firmware path. This does not even work for all platforms, > as hypervisors like VMWare don't expose UEFI as a path, > they

[libvirt] [PATCH 2/3] conf: add support for choosing firmware type

2016-10-03 Thread Daniel P. Berrange
Currently if you want to enable UEFI firmware for a guest you need to know about the hypervisor platform specific firmware path. This does not even work for all platforms, as hypervisors like VMWare don't expose UEFI as a path, they just have a direct config option for turning it on or off. This