Providing builder images for aarch64

[fermino]

Hi, I'm trying to make this work on a RPi 4B, and I noticed that builder images are not currently provided for aarch64.
I'm compiling them from a void install and will give them a test later, but it'd be a nice to have.

I don't think there's any reason why it couldn't be achieved from QEMU, albeit slowly.

What is the current release process for those images? I didn't find anything in GH's workflows, so is it manual? Is there a reason why it couldn't be automated? If not, I guess that running QEMU under ubuntu or even using macos builders could work.

As long as I get it working I could get on this and make a PR, but I'd like to make sure it's aligned with the project :)
Thanks for all the work put into this!!

[classabbyamp]

I had a branch for this, don't remember what state it's in

https://github.com/zbm-dev/zfsbootmenu/tree/multi-platform-drifting

[ahesford]

You'll have to figure out some issues surround kexec on the Raspberry Pi. I don't think Void's kernel will work out of the box. If you manage to get it working, let us know.

[fermino]

Yeah, that was my main concern; I haven't been able to find a lot about what was going on with the rpi4. For now I'm trying to work around this

memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set

[BrianCArnold]

I just got Raspbian booting with root on ZFS, I'm looking for information about kexec not working with the raspbian kernel, but I'm not finding much, and not anything conclusive.

I'm probably going to try to kexec myself from one standard kernel version to another on EXT4, see if that works, keep the ZFS kernel module and all that out of the whole situation first, just get kexec working with standard kernel+initramfs images first.

[classabbyamp]

good luck, it's not a zfs issue, it's almost certainly a hardware/firmware initialization design issue. the raspberry pi boot process is... interesting to say the least, and convoluted at best.

[fermino]

For what I've read it's related to a core parking issue, I've read here that the UEFI implementation does add PSCI, so that might be useful. I'm not sure if the comment is referring to https://github.com/pftf/RPi4, but I've found some issues there referring to PSCI so it might be it.

In the end if it's just a matter of chaining EDK2+ZBM that would be simple compared from a final user perspective instead of having to compile u-boot. I also didn't find any PSCI implementation for u-boot rpi's SOC, but there are some for other ARM platforms.

PS: sorry for kind of hijacking the post about the rpi, please let us know if we should go somewhere else :)

[fermino]

Interesting read: https://web.archive.org/web/20250217163112/https://lig-membres.imag.fr/duble/software/raspberry-pi-netboot/

[bunder2015]

I'm interesting in arm images as well, I recently bought a Radxa Orion O6, which supports UEFI.