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. ** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2036730 Title: autopkgtest ignores --architecture flag Status in autopkgtest package in Ubuntu: Incomplete Status in livecd-rootfs package in Ubuntu: Fix Released Status in autopkgtest source package in Focal: New Status in livecd-rootfs source package in Focal: Triaged Status in autopkgtest source package in Jammy: New Status in livecd-rootfs source package in Jammy: Fix Committed Status in autopkgtest source package in Lunar: New Status in livecd-rootfs source package in Lunar: Fix Committed Status in autopkgtest source package in Mantic: New Status in livecd-rootfs source package in Mantic: In Progress Bug description: Description ----------- The cloud images produced by livecd-rootfs do not properly configure the tty for armhf and subsequently the terminal output is not available. Test Case --------- 1) Run `autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic` substituting the release name as appropriate 2) Observe the last console message `EFI stub: Exiting boot services...` With a cloud image build with the livecd-rootfs version in -proposed you'll see much more output from `autopkgtest-buildvm-ubuntu-cloud` including cloud-init configuring the system. Regression Potential -------------------- The serial console is being set to ttyS0 differently that it was for architectures other than arm64 or armhf. However, this has been in place in noble for an extended period of time and has not cause any regressions for those architectures. Original Description -------------------- On an arm64 as well as on amd64 I saw this behavior: $ autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic $ autopkgtest -U --apt-pocket=proposed -a armhf -s *.dsc -- qemu autopkgtest-mantic-armhf.img autopkgtest [13:18:32]: starting date and time: 2023-09-20 13:18:32+0200 autopkgtest [13:18:32]: version 5.28ubuntu1 autopkgtest [13:18:32]: host mcbin; command line: /usr/bin/autopkgtest -U --apt-pocket=proposed -a armhf -s forensics-all_3.47.dsc -- qemu autopkgtest-mantic-armhf.img qemu-system-aarch64: terminating on signal 15 from pid 3520 (/usr/bin/python3) <VirtSubproc>: failure: timed out waiting for 'login prompt on serial console' autopkgtest [13:19:33]: ERROR: testbed failure: unexpected eof from the testbed When trying to boot into the image on an arm64 system with qemu-system-aarch64 \ -machine virt -accel kvm -m 4G -smp 4 -cpu host,aarch64=off -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=autopkgtest-mantic-armhf.img,if=virtio,format=qcow2 the last messages displayed are EFI stub: Booting Linux Kernel... EFI stub: Entering in SVC mode with MMU enabled EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... qemu-system-aarch64 seems to be close to idling at less than 0.5 % CPU load. So booting obviously stalled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2036730/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
