canonical-ubuntu-qa team mailing list archive

[Skia <2036730@xxxxxxxxxxxxxxxxxx>]

Using the aforementioned merge proposal, I managed to have a cross-
architecture test run on my machine successfully.

Two things:

To get the test to pass, I need to increase the `timeout-reboot` parameter, giving me the following command line:
`autopkgtest -a armhf gzip  -- qemu --timeout-reboot 90 autopkgtest-noble-armhf.img`
Indeed, running the tests in emulation can be quite long, and the default timeout is only 60 seconds, which is quite short for booting a whole system up to the login prompt. (About 65-75 seconds on my machine)


To manually boot the armhf image, here is a working command line:
```
qemu-system-arm \
-machine virt -m 3G -smp 1 -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-noble-armhf.img,if=virtio,format=qcow2
```
A firmware bug indeed prevents using more than 3G of memory, giving the stack trace I saw.

-- 
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:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released

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