srbala/os-autoinst-distri-fedora
1
0
Fork 0
mirror of https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git synced 2025-05-07 18:11:36 +00:00
Code Issues Releases Activity

UEFI: use 4M pflash images to fix DBX updates

Browse Source 
fwupd 2.0.4 is offering DBX updates for openQA tests, and they
seem to fail if we use the 'regular' pflash code/vars images.
Using the 4M images - which apparently provide more space for
EFI variables - seems to work. There's no real downside to using
those images in every test, AFAIK, so let's do that.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2025-01-21 10:07:30 -08:00
parent 4ff2865ff7
commit e9e12b5ff8
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
templates.fif.json
View File

@ -58,8 +58,8 @@
"backend": "qemu", "backend": "qemu",
"settings": { "settings": {
"ARCH_BASE_MACHINE": "64bit", "ARCH_BASE_MACHINE": "64bit",
"INSECURE_PFLASH_CODE": "/usr/share/edk2/ovmf/OVMF_CODE.fd", "INSECURE_PFLASH_CODE": "/usr/share/edk2/ovmf/OVMF_CODE_4M.qcow2",
"INSECURE_PFLASH_VARS": "/usr/share/edk2/ovmf/OVMF_VARS.fd", "INSECURE_PFLASH_VARS": "/usr/share/edk2/ovmf/OVMF_VARS_4M.qcow2",
"PART_TABLE_TYPE": "gpt", "PART_TABLE_TYPE": "gpt",
"QEMUCPU": "host", "QEMUCPU": "host",
"QEMUCPUS": "2", "QEMUCPUS": "2",
@ -72,8 +72,8 @@
"QEMU_MAX_MIGRATION_TIME": "480", "QEMU_MAX_MIGRATION_TIME": "480",
"QEMU_VIRTIO_RNG": "1", "QEMU_VIRTIO_RNG": "1",
"UEFI": "1", "UEFI": "1",
"UEFI_PFLASH_CODE": "/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd", "UEFI_PFLASH_CODE": "/usr/share/edk2/ovmf/OVMF_CODE_4M.secboot.qcow2",
"UEFI_PFLASH_VARS": "/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd", "UEFI_PFLASH_VARS": "/usr/share/edk2/ovmf/OVMF_VARS_4m.secboot.qcow2",
"UEFI_SECURE": "1", "UEFI_SECURE": "1",
"WORKER_CLASS": "qemu_x86_64" "WORKER_CLASS": "qemu_x86_64"
} }