qemu-efi-noacpi/0 no longer works

[Juerg Haefliger]

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

[Paride Legovini (paride)]

This is the very image used in the test runs, in case it helps:

https://people.canonical.com/~paride/priv/adt-kinetic-arm64.bos02.img.gz