From 2a3512fb7197365a898699044b33582a865e19b9 Mon Sep 17 00:00:00 2001 From: Wei Liu Date: Mon, 6 Jul 2026 15:24:34 -0700 Subject: [PATCH] docs: update SEV-SNP build information sev_snp no longer selects a hypervisor backend implicitly. Assisted-by: Copilot:GPT-5.5 Signed-off-by: Wei Liu --- docs/amd_sev_snp.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/amd_sev_snp.md b/docs/amd_sev_snp.md index 97e09a555..d46e763c9 100644 --- a/docs/amd_sev_snp.md +++ b/docs/amd_sev_snp.md @@ -13,14 +13,16 @@ links: A machine with AMD SEV-SNP support which is enabled in the BIOS is required. -On the Cloud Hypervisor side, all you need is to build the project with the -`sev_snp` feature enabled. This enables the MSHV and IGVM support that is -needed by the default SEV-SNP build: +On the Cloud Hypervisor side, build the project with the `sev_snp` and `igvm` +and the hypervisor backend you want to use. For the MSHV SEV-SNP build: ```bash -cargo build --no-default-features --features "sev_snp" +cargo build --no-default-features --features "mshv,sev_snp,igvm" ``` +Change `mshv` to `kvm` for the KVM backend. You can enable both at the same +time. + **Note** Please note that `sev_snp` cannot be enabled in conjunction with the `tdx` feature flag.