please drop console= options from armhf cloud images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
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(
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(
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_
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.
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 AAVMF/AAVMF32_ CODE.fd -drive if=virtio, format= qcow2,file= ubuntu- 21.10-server- cloudimg- armhf.img
qemu-system-arm -M virt -m 4G -smp 4 -nographic -snapshot -bios /usr/share/