[07:12] Jeremy31, thanks [07:13] In the mirror it should be noted as hwe-edge kernel flavor. [11:01] RikMills, yes i would expect that to be the last hwe kernel in 20.04 [11:02] apw: thanks! [11:08] Hello, I'm currently investigating a few issues related to the use of "Secure Encrypted Virtualization (SEV)" on recent kernel. The first one is that the -kvm kernel flavor does not boot when SEV is enabled (LP: #1955395) [11:08] Launchpad bug 1955395 in linux (Ubuntu Jammy) "KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled" [Undecided, Confirmed] https://launchpad.net/bugs/1955395 [11:10] The second one is that kernels starting with 5.11 will not boot with SEV enabled unless swiotlb is forced to be 512Mb (LP but soon to be filed) [11:10] This comes following this commit : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12 [11:10] Commit e998879 in kernel/git/torvalds/linux.git "x86,swiotlb: Adjust SWIOTLB bounce buffer size for SEV guests" [11:11] This sets the SWIOTLB value to 1024Mb and the lowmem allocation fails on recent Ubuntu kernels. The same commit on Fedora 34 kernels (5.13) succeed with the 1024Mb allocation [11:12] oh, just realized that I did create the second bug : LP: #1955655 [11:12] Launchpad bug 1955655 in linux (Ubuntu) "kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param" [Undecided, Confirmed] https://launchpad.net/bugs/1955655 [11:13] I'm currently trying to identify why the lowmem allocation fails on Jammy kernels === gpiccoli_ is now known as gpiccoli