libvirt/tests/qemuxmlconfdata/firmware-manual-noefi-acpi-aarch64.xml

<domain type='qemu'>
  <name>guest</name>
  <uuid>63840878-0deb-4095-97e6-fc444d9bc9fa</uuid>
  <memory unit='KiB'>1048576</memory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='aarch64' machine='virt-4.0'>hvm</type>
  </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>`
tests: Unify input files for firmware tests Most of the differences, such as those in the domain name or amount of memory, are fairly harmless, but they still make it more cumbersome than necessary to directly compare different input (and output) files. More importantly, the use of unversioned machine types in some of the test cases results in the descriptor-based autoselection logic being effectively skipped, because the compatible machine types as listed in them are only the versioned variants. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> 2023-02-08 18:28:05 +00:00			`<uuid>63840878-0deb-4095-97e6-fc444d9bc9fa</uuid>`
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			`<memory unit='KiB'>1048576</memory>`
			`<vcpu placement='static'>1</vcpu>`
			`<os>`
tests: Unify input files for firmware tests Most of the differences, such as those in the domain name or amount of memory, are fairly harmless, but they still make it more cumbersome than necessary to directly compare different input (and output) files. More importantly, the use of unversioned machine types in some of the test cases results in the descriptor-based autoselection logic being effectively skipped, because the compatible machine types as listed in them are only the versioned variants. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> 2023-02-08 18:28:05 +00:00			`<type arch='aarch64' machine='virt-4.0'>hvm</type>`
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>`