canonical-ubuntu-qa team mailing list archive

[John Chittum <2036604@xxxxxxxxxxxxxxxxxx>]

do you know which image this is attempting to boot? the last image we
have produced for arm64:

http://cloud-images.ubuntu.com/mantic/20230823/

It's a bit old, but we've been hitting some major infra issues with
s390x which has prevented publishing. however we don't have any failing
tests over the past few weeks for arm64 mantic images booting in
Openstack

I'm guessing this comes down to how autopkgtest is attempting to launch
the VM, and it's storage backend. Both virtio-blk and virtio-scsi should
be supported at this point, but i'll need more info. Could you link to
how autpkgtest is attempting to launch a vm?

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

Title:
  Synchronous Exception in qemu-system-arm64 VM during autopkgtest-
  buildvm-ubuntu-cloud

Status in cloud-images:
  New
Status in autopkgtest package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  I try to create an autopkgtest VM on an arm64 system with

  autopkgtest-buildvm-ubuntu-cloud -v --release mantic

  or on an amd64 system with

  autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic

  In both cases I get:

  Found linux image: /boot/vmlinuz-6.5.0-5-generic
  Found initrd image: /boot/initrd.img-6.5.0-5-generic
  Found linux image: /boot/vmlinuz-6.3.0-7-generic
  Found initrd image: /boot/initrd.img-6.3.0-7-generic
  Found linux image: /boot/vmlinuz-6.2.0-20-generic
  Found initrd image: /boot/initrd.img-6.2.0-20-generic
  Warning: os-prober will not be executed to detect other bootable partitions.
  BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
  BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)

  
  Synchronous Exception at 0x000000005C328000

  
  Synchronous Exception at 0x000000005C328000
  ^A^Cqemu-system-aarch64: terminating on signal 2
  Traceback (most recent call last):

  /var/crash has no entries.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic aarch64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: pass
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Tue Sep 19 15:37:20 2023
  InstallationDate: Installed on 2021-08-17 (763 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
  KvmCmdLine: COMMAND         STAT  EUID  RUID     PID    PPID %CPU COMMAND
  Lspci-vt:
   -[0000:00]-+-00.0  NVIDIA Corporation GK208B [GeForce GT 730]
              \-00.1  NVIDIA Corporation GK208 HDMI/DP Audio Controller
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  dmi.bios.date: Mar 26 2020
  dmi.bios.release: 1.0
  dmi.bios.vendor: EFI Development Kit II / Marvell
  dmi.bios.version: EDK II
  dmi.board.name: Armada 8040 MacchiatoBin
  dmi.board.vendor: SolidRun
  dmi.board.version: Rev. 1.3
  dmi.chassis.type: 2
  dmi.chassis.vendor: SolidRun
  dmi.chassis.version: Rev. 1.3
  dmi.modalias: dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada8040MacchiatoBin:rvrRev.1.3:cvnSolidRun:ct2:cvrRev.1.3:sku:
  dmi.product.name: Armada 8040 MacchiatoBin
  dmi.product.version: Rev. 1.3
  dmi.sys.vendor: SolidRun

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036604/+subscriptions