I realize there may be licensing issues with packaging OVMF directly with libvirt and virt-manager, but at the very least could the /domain/os/loader element be exposed in virt-manager or virt-install for those of us that can utilize OVMF (or other custom firmwares)?
Is there another UEFI option that is being considered/worked on by the libvirt camp? UEFI is becoming the standard, and it would be nice to have a native virtualization platform that could provide that emulation.
Reference: http://www.linux-kvm.org/page/OVMF#Using_the_firmware_image_with_libvirt
On 08/13/2014 05:33 PM, Dan Mossor wrote:
I realize there may be licensing issues with packaging OVMF directly with libvirt and virt-manager, but at the very least could the /domain/os/loader element be exposed in virt-manager or virt-install for those of us that can utilize OVMF (or other custom firmwares)?
virt-install can set loader, with --boot loader=FOO. You can use the virt-xml tool to alter that for an existing VM.
virt-manager support is actively being looked at, but there's more to it than just exposing the loader value in the UI.
Is there another UEFI option that is being considered/worked on by the libvirt camp? UEFI is becoming the standard, and it would be nice to have a native virtualization platform that could provide that emulation.
Reference: http://www.linux-kvm.org/page/OVMF#Using_the_firmware_image_with_libvirt
Integrating this stuff correctly is under active development at multiple layers of the stack, for example there were additional libvirt patches posted today. So it's definitely on the radar
- Cole
-
Cole Robinson -
Dan Mossor