canonical-ubuntu-qa team mailing list archive

[Paride Legovini <2036730@xxxxxxxxxxxxxxxxxx>]

I'll try to do a recap here to make sure we're on the same page.

1. There was an issue with the armhf images preventing the serial
console to work, and thus preventing autopkgtest(-buildvm-ubuntu-cloud)
to communicate with VMs based on those images. This is now fixed and the
Noble images are working fine.

2. There is a bug in edk2 or qemu (LP: #2043471) preventing qemu-system-
arm to boot armhf images with more than 3GB or RAM or so. This is not a
bug in autopkgtest (and does not affect the autopkgtest-virt-qemu
default RAM size, which is of 1GB). The right place to work on this is
LP: #2043471.

3. We have an annoyance: there is currently no mechanism for
`autopkgtest --architecture` to pass the requested architecture to the
virt server. Ideally we should implement this somehow, e.g. by having
autopkgtest pass the requested architecture to the virt server via an
environment variable. I believe this mechanism should be virt-server-
agnostic (as the env var would be). An approach like [1] entangles two
components that should not be too tightly coupled (autopkgtest and the
virt-server). We can think of good ways to implement this, but this will
make upstreaming the cross-arch testing diff even more difficult (bigger
diff, more design decisions to discuss). Provided that my understanding
here is correct, I propose considering this a documentation issue, and
adding a section to [2] explaining how to properly do cross-arch testing
when using autopkgtest-virt-qemu. What do you think?

[1] https://code.launchpad.net/~hyask/ubuntu/+source/autopkgtest/+git/autopkgtest/+merge/455429
[2] https://wiki.ubuntu.com/ProposedMigration#autopkgtests

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