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 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 adds ability to use the much simpler: > > > > <loader firmware="uefi|bios"/> > > > > to choose the different firmware types. > > Although not in the scope of this patch, virt-v2v would really like > the ESX driver in libvirt to return this data for existing guests. I > believe there is an open RFE about that somewhere. Yep, it should be possile to wire this up to ESX driver based on the existing data in VMX format. 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/ :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list