On 09/16/2014 09:44 AM, Michal Privoznik wrote: > As of 542899168c38 we learned libvirt to use UEFI for domains. > However, management applications may firstly query if libvirt > supports it. And this is where virConnectGetDomainCapabilities() > API comes handy. > > Signed-off-by: Michal Privoznik <[email protected]>
Tested-by: Cole Robinson <[email protected]> Acked-by: Cole Robinson <[email protected]> So this exposes that qemu + libvirt have the required support to use OVMF. The other bit virt-manager would like is to know the paths to the OVMF binaries. Preferably with some way to tell if they actually exist on disk, which might just be hiding them from the XML if they aren't found, or an extra XML property. As you mentioned in the virt-tools-list email, you probably don't need to expose the vars template file path, and just the OVMF binary path. Thoughts on what the XML might look like? Doesn't seem like there's any existing precedence in domcapabilities schema Thanks, Cole -- libvir-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/libvir-list
