2e62081bec
Remove the stale MSHV-only wording now that the docs and CVM test path cover KVM SEV-SNP with IGVM stage0 and fw_cfg [0, 1]. [0]: https://github.com/cloud-hypervisor/cloud-hypervisor/pull/7942 [1]: https://github.com/cloud-hypervisor/cloud-hypervisor/pull/8347 On-behalf-of: SAP philipp.schuster@sap.com Signed-off-by: Philipp Schuster <philipp.schuster@cyberus-technology.de>
1.4 KiB
AMD SEV-SNP
AMD Secure Encrypted Virtualization & Secure Nested Paging (SEV-SNP) is an AMD technology designed to add strong memory integrity protection to help prevent malicious hypervisor-based attacks like data replay, memory-remapping and more in order to create an isolated execution environment. Here are some useful links:
- SNP Homepage: more information about SEV-SNP technical aspects, design and specification.
Cloud Hypervisor support
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:
cargo build --no-default-features --features "sev_snp"
Note
Please note that sev_snp cannot be enabled in conjunction with the tdx feature flag.
SEV-SNP is also supported on KVM with an IGVM stage0 image and a guest kernel
provided through fw_cfg. Build that configuration with:
cargo build --no-default-features --features "kvm,igvm,sev_snp,fw_cfg"
You can run a SEV-SNP VM using the following command:
./cloud-hypervisor \
--platform sev_snp=on \
--cpus boot=1 \
--memory size=1G \
--disk path=ubuntu.img
For more information related to Microsoft Hypervisor, please see mshv.md.