I've done some initial work to generate Arm images, but there's some bikeshedding to do before it's ready to upload.
Is there a consensus on a prefix for the Arm "VMF" images? OpenStack Nova hardcodes "/usr/share/AAVMF/AAVMF_CODE.fd" for AArch64, but it doesn't have Arm support yet apparently. Is there any need for the QEMU_EFI.fd artifact on ARM? We deliver both the QEMU_EFI.fd and AAVMF images for AArch64, but I don't know if anyone uses the QEMU_EFI.fd images themselves, and I'd rather not continue delivering the same code twice. Finally, I think when we start adding new images (Arm/32-bit), we should do so under a cleaner packaging layout. See #842690 for a proposal there. -dann
