Dann, Regarding the 2nd option you listed: "Switch the xenial cloud-images to use the HWE kernel. There's precedent for this (we did it for trusty to add support for GICv3 systems). Existing VMs using 4.4 will still break after upgrading qemu-efi past xenial."
As you know, the prior change to a Trusty images was made after determining that there were no supported systems on the market with GICv2 hardware; the impact of that change was deemed minimal. A change in cloud images to move from the GA to HWE kernel for an arm xenial image could be disruptive and we would need to weigh the risks and impact of that. I think you know that well already, I just wanted to reinforce that position and encourage edk2 and kernel developers to investigate remediation in those areas first. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744754 Title: qemu-efi-aarch64 in >= artful can't boot xenial cloud images Status in cloud-images: New Status in edk2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in edk2 source package in Xenial: New Status in linux source package in Xenial: Incomplete Bug description: [Impact] After upgrading your KVM hypervisor past xenial, your xenial-based guests will fail to boot. [Test Case] Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic. [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1744754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
