Hi,
> > > If you want to boot a guest using EDK2, you should use the images
> > > build by your distribution (/usr/share/qemu/edk2-aarch64-code.fd),
> > > not these images.
> Then we should add edk2-aarch64 and edk2-ovmf to lcitool, to have
> the distrib images in our generated Docker images.
>
> Cleber, you added this test in commit 6fd52d671d ("Acceptance test:
> add "boot_linux" tests"), can you have a look?
Well, it's not *that* simple. Names are not consistent across
distributions. I think if we want go that route we have to inspect
the *.json files in /usr/share/qemu/firmware to find the correct
distro firmware images.
Also note that at least fedora ships both verbose and non-verbose
images ...
kraxel@sirius ~# rpm -ql edk2-aarch64
[ ... ]
/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw
/usr/share/edk2/aarch64/QEMU_EFI-silent-pflash.raw
/usr/share/edk2/aarch64/QEMU_EFI.fd
/usr/share/edk2/aarch64/QEMU_EFI.silent.fd
/usr/share/edk2/aarch64/QEMU_VARS.fd
[ ... ]
/usr/share/qemu/firmware/60-edk2-aarch64.json
/usr/share/qemu/firmware/70-edk2-aarch64-verbose.json
... so maybe it is an option to use the distro images for the bios
tables test cases too.
take care,
Gerd
