Comment 40 for bug 2036730

My test case in the description is actually incorrect as an armhf cloud image would need to be built with the version of livecd-rootfs from -proposed. Phil Roche did build those images for me though and I downloaded them from https://private-fileshare.canonical.com/~philroche/LP-2036730/. After which I booted the image with the following command (also seen in a previous comment of mine).

 $ qemu-system-aarch64 \
-machine virt -m 4G -smp 4 -nographic \
-object rng-random,filename=/dev/urandom,id=rng0 \
-device virtio-rng-pci,rng=rng0,id=rng-device0 \
-drive if=pflash,format=raw,unit=0,read-only=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd \
-device virtio-net-pci,netdev=eth0 \
-netdev user,id=eth0,hostfwd=tcp::8022-:22 \
-drive file=lunar-server-cloudimg-armhf.img,if=virtio,format=qcow2

With the current daily lunar-server-cloudimg-armhf.img file I never saw any output when booting the image other than:

EFI stub: Booting Linux Kernel...
EFI stub: Entering in SVC mode with MMU enabled
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services...

With the image build with the version of livecd-rootfs from -proposed I saw the full boot sequence and was presented with a log-in prompt.

Ubuntu 23.04 ubuntu ttyAMA0
....
[ 253.999776] cloud-init[1368]: 2023-12-12 17:58:11,049 - cc_final_message.py[WARNING]: Used fallback datasource
[ OK ] Finished cloud-final.servi… Execute cloud user/final scripts.
[ OK ] Reached target cloud-init.target - Cloud-init target.

ubuntu login: ubuntu

So I'm setting this to verification-done for Lunar.