please drop console= options from armhf cloud images

[dann frazier]

I tried booting an armhf cloudimage (today's impish daily) in a KVM guest, and observed no output following the EFI stub:

-----------
$ virsh start imphf && virsh console imphf
Domain imphf started

Connected to domain imphf
Escape character is ^]
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)
EFI stub: Entering in SVC mode with MMU enabled
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
-----------

Turns out, the problem was that the console parameters are incorrect:

GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0"

The QEMU's virt machine type has an emulated PL011 serial port, which is automatically detected w/o the need for any console= parameter (the device is actually ttyAMA0). So, like arm64, there's no need to specify any console= setting.

[Gauthier Jolly (gjolly)]

Hi Dann,

Thanks for reporting this bug. I confirm that I can reproduce the issue:

Steps to reproduce (even on amd64):
Requirements qemu-system-arm and qemu-efi-arm

curl -sLO http://cloud-images.ubuntu.com/releases/impish/release/ubuntu-21.10-server-cloudimg-armhf.img
qemu-system-arm -M virt -m 4G -smp 4 -nographic -snapshot -bios /usr/share/AAVMF/AAVMF32_CODE.fd -drive if=virtio,format=qcow2,file=ubuntu-21.10-server-cloudimg-armhf.img

[Gauthier Jolly (gjolly)]

This is most likely due to this bug[0] and this commit[1]. Fortunately, it has not been SRUed.

[0] https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1925780
[1] https://git.launchpad.net/livecd-rootfs/commit/live-build?h=41fd537bc22fded83127cd7871b1ee3d7fe9656e

[Simon Piette (simon.piette)]

It looks like the same issue here: https://bugs.launchpad.net/cloud-images/+bug/1785633