On 07/10/2018 04:51 PM, Cole Robinson wrote: > On 07/10/2018 04:22 PM, Zbigniew Jędrzejewski-Szmek wrote: >> On Tue, Jul 03, 2018 at 10:14:43PM -0700, Thomas Daede wrote: >>> On 07/03/2018 05:15 AM, Jan Kurik wrote: >>>> Move to uEFI as the default boot mechanism for ARMv7 devices. >>> Will this work with virt-manager too? Currently, while aarch64 boots via >>> uEFI there, it seems that armv7 is only supported by manually specifying >>> a kernel and initrd. >> Ping. >> > Currently this won't work with virt-manager. > > If this arm32 stuff works similar to aarch64, then what we need is: > extend the edk2 package to build working arm32 images, some packaging > changes to libvirt, and some straightforward-but-not-trivial changes to > virt-manager to match. > > Gerd Hoffman has a nightly edk2 repo which builds arm32 images. If > someone can figure out the magic qemu incantation to get those working > with Fedora, similar to how aarch64 works, I can do the rest Is it not the usual "-drive file=OVMF_CODE.fd,format=raw,readonly=on,if=plfash" on a "-machine virt" type of VM? _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/4VGRHWACRQGJ6ODR6WQZXRGJCGMTUDWI/
