canonical-ubuntu-qa team mailing list archive

[Heinrich Schuchardt <2036730@xxxxxxxxxxxxxxxxxx>]

A login into the image is possible via U-Boot:

qemu-system-arm -machine virt -cpu cortex-a15 -m 1G -smp cores=2 -bios
/usr/lib/u-boot/qemu_arm/u-boot.bin -nographic -object rng-
random,filename=/dev/urandom,id=rng0 -device virtio-rng-
pci,rng=rng0,id=rng-device0 -device virtio-net-pci,netdev=eth0 -netdev
user,id=eth0,hostfwd=tcp::8022-:22 -drive file=autopkgtest-mantic-
armhf.img,if=virtio,format=qcow2

In the U-Boot console use

virtio scan
load virtio 0:1 $kernel_addr_r boot/vmlinuz 
load virtio 0:1 $ramdisk_addr_r boot/initrd.img
setenv bootargs root=/dev/vda1
bootz $kernel_addr_r $ramdisk_addr_r:$filesize $fdtcontroladdr

grub.cfg has this line:

linux /boot/vmlinuz-6.5.0-5-generic root=LABEL=cloudimg-rootfs ro
console=tty1 console=ttyS0

But the last command indicates that the serial console is ttyAMA0:

ubuntu@autopkgtest:~$ last
ubuntu   ttyAMA0                       Wed Sep 20 13:50   still logged in
reboot   system boot  6.5.0-5-generic  Wed Sep 20 13:43   still running

File /etc/default/grub.d/50-cloudimg-settings.cfg introduces the
console=ttyS0 commandline argument.

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