canonical-ubuntu-qa team mailing list archive

[Juerg Haefliger <1992738@xxxxxxxxxxxxxxxxxx>]

** Attachment added: "adt.log"
   https://bugs.launchpad.net/auto-package-testing/+bug/1992738/+attachment/5623813/+files/adt.log

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/1992738

Title:
  qemu-efi-noacpi/0 no longer works

Status in Auto Package Testing:
  New

Bug description:
  Since a couple of weeks ago, the magic trigger qemu-efi-noacpi/0 no
  longer works. By no longer works I mean that the special script that
  sets the ForceNoAcpi EFI variable is run and the VM comes back with
  ACPI disabled after the first reboot following the testbed setup. But
  for unknown reasons, the VM reboots a second time ~2mins later and
  then returns with ACPI enabled again. From the journald log it looks
  almost like the VM crashes or is rebooted/reset from the outside since
  nothing indicates a scheduled or deliberate reboot. Also, the EFI
  variable setting is sticky and a simple reboot should not clear it.

  In the attached log:
  Boot 2740f9ab9bc145f98ee76f4ae8e6d10e - First boot of ADT VM
  Boot 3beaf1a829084828afe7fbf2f241d11b - 1st scheduled reboot after testbed setup
  Boot f69f7e8df6264ef8a425ccaa95be5f70 - 2nd unexpected reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1992738/+subscriptions