mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-07-06 09:55:46 +00:00
10a8997cbb
Due to the way the information is stored by the XML parser, we've had this quirk where specifying any information about the loader or NVRAM would implicitly set its format to raw. That is, <nvram>/path/to/guest_VARS.fd</nvram> would effectively be interpreted as <nvram format='raw'>/path/to/guest_VARS.fd</nvram> forcing the use of raw format firmware even when qcow2 format would normally be preferred based on the ordering of firmware descriptors. This behavior can be worked around in a number of ways, but it's fairly unintuitive. In order to remove this quirk, move the selection of the default firmware format from the parser down to the individual drivers. Most drivers only support raw firmware images, so they can unconditionally set the format early and be done with it; the QEMU driver, however, supports multiple formats and so in that case we want this default to be applied as late as possible, when we have already ruled out the possibility of using qcow2 formatted firmware images. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> |
||
|---|---|---|
| .. | ||
| bhyve_capabilities.c | ||
| bhyve_capabilities.h | ||
| bhyve_command.c | ||
| bhyve_command.h | ||
| bhyve_conf.c | ||
| bhyve_conf.h | ||
| bhyve_device.c | ||
| bhyve_device.h | ||
| bhyve_domain.c | ||
| bhyve_domain.h | ||
| bhyve_driver.c | ||
| bhyve_driver.h | ||
| bhyve_firmware.c | ||
| bhyve_firmware.h | ||
| bhyve_monitor.c | ||
| bhyve_monitor.h | ||
| bhyve_parse_command.c | ||
| bhyve_parse_command.h | ||
| bhyve_process.c | ||
| bhyve_process.h | ||
| bhyve_utils.h | ||
| bhyve.conf | ||
| libvirtd_bhyve.aug | ||
| meson.build | ||
| test_libvirtd_bhyve.aug.in | ||