mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-11-05 12:51:12 +00:00
5b9819eedc
If a management application wants to use firmware auto selection
feature it can't currently know if the libvirtd it's talking to
support is or not. Moreover, it doesn't know which values that
are accepted for the @firmware attribute of <os/> when parsing
will allow successful start of the domain later, i.e. if the mgmt
application wants to use 'bios' whether there exists a FW
descriptor in the system that describes bios.
This commit then adds 'firmware' enum to <os/> element in
<domainCapabilities/> XML like this:
<enum name='firmware'>
<value>bios</value>
<value>efi</value>
</enum>
We can see both 'bios' and 'efi' listed which means that there
are descriptors for both found in the system (matched with the
machine type and architecture reported in the domain capabilities
earlier and not shown here).
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Acked-by: Laszlo Ersek <lersek@redhat.com>
|
||
|---|---|---|
| .. | ||
| bhyve_basic.x86_64.xml | ||
| bhyve_fbuf.x86_64.xml | ||
| bhyve_uefi.x86_64.xml | ||
| empty.xml | ||
| libxl-xenfv.xml | ||
| libxl-xenpv.xml | ||
| qemu_1.7.0.x86_64.xml | ||
| qemu_2.6.0-virt.aarch64.xml | ||
| qemu_2.6.0.aarch64.xml | ||
| qemu_2.6.0.ppc64.xml | ||
| qemu_2.6.0.x86_64.xml | ||
| qemu_2.7.0.s390x.xml | ||
| qemu_2.8.0-tcg.x86_64.xml | ||
| qemu_2.8.0.s390x.xml | ||
| qemu_2.8.0.x86_64.xml | ||
| qemu_2.9.0-q35.x86_64.xml | ||
| qemu_2.9.0-tcg.x86_64.xml | ||
| qemu_2.9.0.x86_64.xml | ||
| qemu_2.12.0-virt.aarch64.xml | ||
| qemu_2.12.0.ppc64.xml | ||
| qemu_2.12.0.s390x.xml | ||
| qemu_2.12.0.x86_64.xml | ||
| qemu_3.0.0.s390x.xml | ||
| qemu_3.1.0.x86_64.xml | ||
| qemu_4.0.0.x86_64.xml | ||