This bug is awaiting verification that the linux-gcp/6.14.0-1011.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-plucky-linux-gcp' to 'verification-done-plucky- linux-gcp'. If the problem still exists, change the tag 'verification- needed-plucky-linux-gcp' to 'verification-failed-plucky-linux-gcp'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-plucky-linux-gcp-v2 verification-needed-plucky-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2116545 Title: Attestation failure due to vTPM device error Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Noble: In Progress Status in linux-gcp source package in Plucky: In Progress Status in linux-gcp source package in Questing: In Progress Bug description: SRU Justification: [Impact] Google requests that the following upstream commits be removed from 6.14 kernels, namely plucky:linux-gcp and noble:linux-gcp-6.14. These commits are responsible for a TPM failure encountered on their TDX- enabled deployments. When present, the following error message is observed during boot and the TPM is not available. TPM fail - No TPM chip found [Fix] By reverting these two commits, the resulting kernel was verified to not exhibit the failing case. 6a5abeea9c72e1d2c538622b4cf66c80cc816fd3 ("x86/mtrr: Rename mtrr_overwrite_state() to guest_force_mtrr_state()") 8e690b817e38769dc2fa0e7473e5a5dc1fc25795 ("x86/kvm: Override default caching mode for SEV-SNP and TDX") [Test Plan] The fix has been verified to work both internally on TDX hardware and independently by Google. [What could go wrong] This change is considered low risk as the commits were cleanly reverted, and the resulting kernel has been verified to resolve the issue both internally and by Google. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2116545/+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
