>From the upstream discussion on the linux-pci mailing list [*]: > Yes. My understanding is that the issue is because AWS is using older > versions of Xen. They are in the process of updating their fleet to a > newer version of Xen so the change introduced with Stefan's commit > isn't an issue any longer. > > I think the changes are scheduled to be completed in the next 10-12 > weeks. For now we are carrying a revert in the Fedora Kernel. > > You can follow this Fedora CoreOS issue if you'd like to know more > about when the change lands in their backend. We work closely with one > of their partner engineers and he keeps us updated. > https://github.com/coreos/fedora-coreos-tracker/issues/1066
Ideally we can revert the upstream commit from the stable kernels, since otherwise Debian users on AWS Xen instance types may be stuck using older, unsafe kernels. Especially if we have time to include the change in the upcoming bullseye and buster point releases. If the kernel updates for those stable updates have already been built, though, it might be too late to matter. By the time we publish our next kernel builds, the AWS Xen update may be complete. noah * https://lore.kernel.org/linux-pci/c4a65b9a-d1e2-bf0d-2519-aac718593...@redhat.com/
