I don't think this is an EDK2 bug anymore, it looks more like a qemu-system-arm bug. AAVMF32 + armhf kernel boots fine in qemu-system-aarch64 with 8GiB of RAM:
```
qemu-system-aarch64 \
-machine virt \
-m 8G \
-drive if=pflash,format=raw,unit=0,readonly=on,file=AAVMF32_CODE.fd \
-drive if=pflash,format=raw,unit=1,file=AAVMF32_VARS.fd \
-drive file=autopkgtest-noble-armhf.img,if=virtio,format=qcow2
```
I don't think this is an EDK2 bug anymore, it looks more like a qemu-system-arm bug. AAVMF32 + armhf kernel boots fine in qemu-system-aarch64 with 8GiB of RAM: format= raw,unit= 0,readonly= on,file= AAVMF32_ CODE.fd \ format= raw,unit= 1,file= AAVMF32_ VARS.fd \ t-noble- armhf.img, if=virtio, format= qcow2
```
qemu-system-aarch64 \
-machine virt \
-m 8G \
-drive if=pflash,
-drive if=pflash,
-drive file=autopkgtes
```