libvirt/tests/qemuxml2argvdata/firmware-auto-efi-loader-path.xml

<domain type='kvm'>
  <name>fedora</name>
  <uuid>63840878-0deb-4095-97e6-fc444d9bc9fa</uuid>
  <memory unit='KiB'>8192</memory>
  <vcpu placement='static'>1</vcpu>
  <os firmware='efi'>
    <type arch='x86_64' machine='pc-q35-4.0'>hvm</type>
    <loader>/path/to/OVMF_CODE.fd</loader>
  </os>
  <features>
    <acpi/>
  </features>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <controller type='usb' model='none'/>
    <memballoon model='none'/>
  </devices>
</domain>
conf: Validate firmware configuration more thoroughly Generally speaking, when firmware autoselection is in use we don't want any information to be provided manually. There are two exceptions: * we still want the path to the NVRAM file to be customizable; * using <loader secure='yes'/> was how you would ask for a firmware that implements the Secure Boot feature in the original approach to firmware autoselection, so we want to keep that working. Anything else should result in a descriptive error. Resolves: https://gitlab.com/libvirt/libvirt/-/issues/327 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> 2022-06-15 10:00:58 +00:00			`<domain type='kvm'>`
			`<name>fedora</name>`
			`<uuid>63840878-0deb-4095-97e6-fc444d9bc9fa</uuid>`
			`<memory unit='KiB'>8192</memory>`
			`<vcpu placement='static'>1</vcpu>`
			`<os firmware='efi'>`
			`<type arch='x86_64' machine='pc-q35-4.0'>hvm</type>`
			`<loader>/path/to/OVMF_CODE.fd</loader>`
			`</os>`
			`<features>`
			`<acpi/>`
			`</features>`
			`<devices>`
			`<emulator>/usr/bin/qemu-system-x86_64</emulator>`
			`<controller type='usb' model='none'/>`
			`<memballoon model='none'/>`
			`</devices>`
			`</domain>`