libvirt/tests/qemuxmlconfdata/firmware-auto-efi-enrolled-keys.xml

<domain type='kvm'>
  <name>guest</name>
  <uuid>63840878-0deb-4095-97e6-fc444d9bc9fa</uuid>
  <memory unit='KiB'>1048576</memory>
  <vcpu placement='static'>1</vcpu>
  <os firmware='efi'>
    <type arch='x86_64' machine='pc-q35-4.0'>hvm</type>
    <firmware>
      <feature enabled='yes' name='enrolled-keys'/>
    </firmware>
  </os>
  <features>
    <acpi/>
  </features>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <controller type='usb' model='none'/>
    <memballoon model='none'/>
  </devices>
</domain>
tests: Add more firmware tests Note that some of these new tests are displaying incorrect or suboptimal behavior. When we address those in upcoming patches, this will be highlighted by changes in the test data. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> 2022-06-09 13:56:32 +00:00			`<domain type='kvm'>`
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			`<name>guest</name>`
tests: Add more firmware tests Note that some of these new tests are displaying incorrect or suboptimal behavior. When we address those in upcoming patches, this will be highlighted by changes in the test data. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> 2022-06-09 13:56:32 +00:00			`<uuid>63840878-0deb-4095-97e6-fc444d9bc9fa</uuid>`
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			`<memory unit='KiB'>1048576</memory>`
tests: Add more firmware tests Note that some of these new tests are displaying incorrect or suboptimal behavior. When we address those in upcoming patches, this will be highlighted by changes in the test data. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> 2022-06-09 13:56:32 +00:00			`<vcpu placement='static'>1</vcpu>`
			`<os firmware='efi'>`
			`<type arch='x86_64' machine='pc-q35-4.0'>hvm</type>`
			`<firmware>`
			`<feature enabled='yes' name='enrolled-keys'/>`
			`</firmware>`
			`</os>`
			`<features>`
			`<acpi/>`
			`</features>`
			`<devices>`
			`<emulator>/usr/bin/qemu-system-x86_64</emulator>`
			`<controller type='usb' model='none'/>`
			`<memballoon model='none'/>`
			`</devices>`
			`</domain>`