canonical-ubuntu-qa team mailing list archive

[Heinrich Schuchardt <2036730@xxxxxxxxxxxxxxxxxx>]

"autopkgtest-buildvm-ubuntu-cloud -v --arch armhf --release mantic" on
amd64 launches QEMU as

qemu-system-arm -machine virt -m 512 -smp 1 -nographic -net
nic,model=virtio -net user,hostfwd=tcp:127.0.0.1:10022-:22 -object rng-
random,filename=/dev/urandom,id=rng0 -device virtio-rng-
pci,rng=rng0,id=rng-device0 -monitor unix:/tmp/autopkgtest-
qemu.n4bb59zs/monitor,server=on,wait=off -virtfs
local,id=autopkgtest,path=/tmp/autopkgtest-
qemu.n4bb59zs/shared,security_model=none,mount_tag=autopkgtest -device
virtio-serial -chardev socket,path=/tmp/autopkgtest-
qemu.n4bb59zs/hvc0,server=on,wait=off,id=hvc0 -device
virtconsole,chardev=hvc0 -chardev socket,path=/tmp/autopkgtest-
qemu.n4bb59zs/hvc1,server=on,wait=off,id=hvc1 -device
virtconsole,chardev=hvc1 -serial unix:/tmp/autopkgtest-
qemu.n4bb59zs/ttyS0,server=on,wait=off -drive
index=0,file=/tmp/autopkgtest-buildvm-ubuntu-cloud1bu3xpgi/mantic-
server-cloudimg-armhf.img,format=qcow2,if=virtio,discard=unmap -drive
index=1,file=/tmp/autopkgtest-buildvm-ubuntu-
cloud1bu3xpgi/autopkgtest.seed,format=raw,if=virtio,discard=unmap,readonly
-drive if=pflash,format=raw,unit=0,read-
only=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd -drive
if=pflash,format=raw,unit=1,file=/tmp/autopkgtest-
qemu.n4bb59zs/efivars.fd

So here the QEMU architecture looks right.

When I run this command I see no issue except for missing feedback to
the user for many minutes:

BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
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...
Moving image into final destination ./autopkgtest-mantic-armhf.img

The problem here seems to be using console=/dev/ttyS0 instead of
console=/dev/ttyAMA0 on the kernel command line.

So we have two separate issues to resolve:

- serial console on the command line for armhf images
- setting --qemu-architecture=arm for the 'autopkgtest -a armhf' command.

-- 
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:
  New

Bug 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