]> git.ipfire.org Git - thirdparty/libvirt.git/commit
qemu: Generate NVRAM path in more cases
authorAndrea Bolognani <abologna@redhat.com>
Fri, 26 May 2023 12:40:02 +0000 (14:40 +0200)
committerAndrea Bolognani <abologna@redhat.com>
Mon, 21 Aug 2023 11:51:30 +0000 (13:51 +0200)
commitccbb987707e282af8d7f8c0db47e70fdebab959f
tree4d83040bfbc2b9a5a61be3eccd553b76e1b25675
parent4a49114ff47d4a9432d211200f734886f9ce200b
qemu: Generate NVRAM path in more cases

Right now, we only generate it after finding a matching entry
either among firmware descriptors or in the legacy firmware
list.

Even if the domain is configured to use a custom firmware build
that we know nothing about, however, we should still automatically
generate the NVRAM path instead of requiring the user to provide
it manually.

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
src/qemu/qemu_firmware.c
tests/qemuxml2argvdata/firmware-manual-efi-loader-path-nonstandard.x86_64-latest.args [new file with mode: 0644]
tests/qemuxml2argvdata/firmware-manual-efi-loader-path-nonstandard.x86_64-latest.err [deleted file]
tests/qemuxml2argvdata/firmware-manual-efi-nvram-template-nonstandard.x86_64-latest.args [new file with mode: 0644]
tests/qemuxml2argvdata/firmware-manual-efi-nvram-template-nonstandard.x86_64-latest.err [deleted file]
tests/qemuxml2argvtest.c
tests/qemuxml2xmloutdata/firmware-manual-efi-loader-path-nonstandard.x86_64-latest.xml
tests/qemuxml2xmloutdata/firmware-manual-efi-nvram-template-nonstandard.x86_64-latest.xml