-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(RHEL-50651) Fix detection of TDX confidential VM on Azure platform #296
(RHEL-50651) Fix detection of TDX confidential VM on Azure platform #296
Conversation
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> (cherry picked from commit 129b9e3) Related: RHEL-50651
This helper is a simplified version of detect_confidential_virtualization() that merely returns a boolean status flag reflecting whether we are believed to be running inside a confidential VM. This flag can be used for turning off features that are inappropriate to use from a CVM, but must not be used for releasing sensitive data. The latter must only be done in response to an attestation for the environment. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> (cherry picked from commit b354a2c) Related: RHEL-50651
In a confidential VM, the SMBIOS data is not trusted, as it is under the control of the host OS/admin and not covered by attestation of the machine. Fixes: systemd/systemd#27604 Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> (cherry picked from commit 4b1153c) Related: RHEL-50651
The original CVM detection logic for TDX assumes that the guest can see the standard TDX CPUID leaf. This was true in Azure when this code was originally written, however, current Azure now blocks that leaf in the paravisor. Instead it is required to use the same Azure specific CPUID leaf that is used for SEV-SNP detection, which reports the VM isolation type. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> (cherry picked from commit 9d7be044cad1ae54e344daf8f2ec37da46faf0fd) Related: RHEL-50651
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Commit validationTracker - RHEL-50651 The following commits meet all requirements
Tracker validationSuccess🟢 Tracker RHEL-50651 has set desired product: Pull Request validationSuccess🟢 CI - All checks have passed Auto MergeSuccess🟢 Pull Request is not marked as draft and it's not blocked by |
Related: RHEL-50651