Repository navigation
Conversation
Signed-off-by: Hang Yin <h4x3rotab@gmail.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a plan for a native SEV-SNP hardware key provider so dstack KMS can recover persistent state on AMD CVMs. Keep KMS service logic and application protocols unchanged, and defer native TDX sealing based on the DGX B300 probe.
Record the completed SNP hardware checks: repeated explicit-VCEK derivation, recovery after a fresh QEMU launch, a different key after a HOST_DATA change, and recovery of the original key after restoring it. These passed in a disposable Cloud CVM without host or guest kernel changes. Provider integration, end-to-end KMS recovery, physical-host reboot, and firmware-update tests remain pending.
Validation for this documentation change:
prek run --files docs/amd-sev-snp-kms-plan.md,reuse lint, relative-link checks, and a check that infrastructure details are omitted.