@Robert: Actually, X-Gene is supported on trusty, which is non-GICv3, but your point is taken. I personally think option #3 would be the best option, but wasn't sure of the feasibility. However, I've been working on the necessary kernel backports in the background over the past week, and I now have something working that looks pretty clean/minimal. I'm doing some regression testing now, and plan to submit to the kernel team later this week.
** Changed in: linux (Ubuntu Xenial) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: edk2 (Ubuntu Xenial) Status: New => Invalid -- 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: Fix Released Status in edk2 source package in Xenial: Invalid Status in linux source package in Xenial: In Progress 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