Thanks for the update - will this be backported to Noble too? That's what Github Actions runner use. Thanks!
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2106673 Title: KVM-AMD Crash in GitHub Actions Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Noble: Fix Committed Status in linux-azure source package in Oracular: Fix Committed Status in linux-azure source package in Plucky: Fix Committed Status in linux-azure source package in Questing: Fix Committed Bug description: SRU Justification [ Impact ] * Microsoft request to fix hyperv when nested kvm guest launched using Secure Boot [ Fix ] * SAUCE (no-up) patch on LKML under RFC "KVM: SVM: Workaround overly strict CR3 check by Hyper-V" [ Test Plan ] * Compile tested * Microsoft to test further [ Where problems could occur ] * This patch modifies some behavior of KVM and prevents putting regular values in the CR3 register which cause problems with Hyper-V. The change is localized, but could cause regressions in Hyper-V virtualization if a code path depends on these values in CR3. [ Other info ] * SF#00409185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2106673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
