External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-05 21:01:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
813ccd553b
libvirt/tests/qemuxml2argvdata/firmware-manual-efi-loader-no-path.xml

19 lines
485 B
XML
Raw Normal View History

tests: add explicit test case for pflash loader lacking path The following is expected to raise an error: <os> <loader readonly='yes' type='pflash'/> </os> because no path to the pflash loader is given and there is no default built-in. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-02-07 12:45:38 +00:00
<domain type='qemu'>
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>
<uuid>63840878-0deb-4095-97e6-fc444d9bc9fa</uuid>
tests: add explicit test case for pflash loader lacking path The following is expected to raise an error: <os> <loader readonly='yes' type='pflash'/> </os> because no path to the pflash loader is given and there is no default built-in. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-02-07 12:45:38 +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='x86_64' machine='pc-i440fx-4.0'>hvm</type>
tests: add explicit test case for pflash loader lacking path The following is expected to raise an error: <os> <loader readonly='yes' type='pflash'/> </os> because no path to the pflash loader is given and there is no default built-in. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-02-07 12:45:38 +00:00
<loader readonly='yes' type='pflash'/>
</os>
<features>
<acpi/>
</features>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</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'/>
<memballoon model='none'/>
tests: add explicit test case for pflash loader lacking path The following is expected to raise an error: <os> <loader readonly='yes' type='pflash'/> </os> because no path to the pflash loader is given and there is no default built-in. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-02-07 12:45:38 +00:00
</devices>
</domain>
Reference in New Issue Copy Permalink