Hi, Booting armv7 machines is pretty messy, and fedora seems to support uboot only for them. There isn't a armv7 build of grub2 ... qemu virtual machines (-M virt machine type) look pretty much identical for armv7 and aarch64 (except for the cpu obviously). tianocore firmware works for both. The fedora kernel works fine too, when loaded directly via -kernel. I've updated the edk2 package to also build arm firmware images (edk2-arm subpackage), which should land in -testing soon. The only thing missing now is a bootloader, so you don't have to copy the kernel + initrd images from the virtual disk somehow to boot the virtual machine (and repeat that procedure after every kernel update). Tried to build the grub2 fedora package on arm. Didn't work out, fails with a apparently secure-boot related build failure. Went on with upstream grub2 instead, added two patches[1][2] to make grub look up the FDT and pass it on to the guest. That works. Not fully sure this is the best way to handle things though. Noticed the guest kernel doesn't know it runs on efi (/sys/firmware/efi is not there). Guess because grub doesn't enter the kernel via efi stub. Suggestions how to go forward? I think once we have grub2 @ arm installing virtual machines should be as easy as it is on aarch64 and x86. cheers, Gerd [1] https://lists.gnu.org/archive/html/bug-grub/2016-07/msg00014.html [2] https://lists.gnu.org/archive/html/bug-grub/2016-07/msg00016.html _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx
