libvirt/tests/qemuxml2argvdata/firmware-manual-efi-acpi-aarch64.xml

<domain type='qemu'>
  <name>guest</name>
  <uuid>496d7ea8-9739-544b-4ebd-ef08be936e8b</uuid>
  <memory unit='KiB'>1048576</memory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='aarch64' machine='virt'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/AAVMF/AAVMF_CODE.fd</loader>
    <nvram>/some/user/nvram/path/guest_VARS.fd</nvram>
  </os>
  <features>
    <acpi/>
  </features>
  <devices>
    <emulator>/usr/bin/qemu-system-aarch64</emulator>
    <controller type='usb' model='none'/>
    <memballoon model='none'/>
  </devices>
</domain>
tests: Test ACPI, UEFI requirements Make sure every combination of ACPI and UEFI works, or fails to work, as expected. 2017-03-09 15:38:56 +00:00			`<domain type='qemu'>`
			`<name>guest</name>`
			`<uuid>496d7ea8-9739-544b-4ebd-ef08be936e8b</uuid>`
			`<memory unit='KiB'>1048576</memory>`
			`<vcpu placement='static'>1</vcpu>`
			`<os>`
			`<type arch='aarch64' machine='virt'>hvm</type>`
			`<loader readonly='yes' type='pflash'>/usr/share/AAVMF/AAVMF_CODE.fd</loader>`
tests: don't use auto-generated NVRAM path in tests By using the auto-generated NVRAM path in test data files, we won't see bugs where a user specified path gets accidentally overwritten by a post-parse callback, or VM startup. For example, this caused us to miss the bug fixed by: commit 24adb6c7a6cbd8ce5f9de67e6af5d89e0e57c270 Author: Michal Prívozník <mprivozn@redhat.com> Date: Wed Feb 23 08:50:44 2022 +0100 qemu: Don't regenerate NVRAM path if parsed from domain XML Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2022-02-23 12:45:51 +00:00			`<nvram>/some/user/nvram/path/guest_VARS.fd</nvram>`
tests: Test ACPI, UEFI requirements Make sure every combination of ACPI and UEFI works, or fails to work, as expected. 2017-03-09 15:38:56 +00:00			`</os>`
			`<features>`
			`<acpi/>`
			`</features>`
			`<devices>`
			`<emulator>/usr/bin/qemu-system-aarch64</emulator>`
tests: Use minimal hardware for firmware tests When testing firmware selection, we don't really care about any of the hardware assigned to the VM, and in fact it's better to keep it as minimal as possible to make sure that the focus remains on the firmware bits. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> 2022-06-09 13:02:19 +00:00			`<controller type='usb' model='none'/>`
tests: Test ACPI, UEFI requirements Make sure every combination of ACPI and UEFI works, or fails to work, as expected. 2017-03-09 15:38:56 +00:00			`<memballoon model='none'/>`
			`</devices>`
			`</domain>`