The Common Challenges of Secure VMs
summary
Overview of concrete problems and solutions for running encrypted VMs: memory is encrypted per-VM keys in hardware (AMD SEV/SNP, IBM secure execution, Intel TDX announced) but key slots are few so only a limited number of secure VMs can run; IO and device DMA need bounce buffers or unprotected IO pages and cause exceptions; swapping requires the trusted entity to encrypt/decrypt and integrity-check pages; migration needs encrypted, integrity-checked state and cross-host key escrow; tooling gaps include SV tools, QEMU/KVM hooks and cgroup limits.
AI-written summary · about
chapters (15)
- 0:00Secure VM challenges
- 1:31What are secure VMs
- 3:38Secure VM architectures
- 5:04Runtime protection techniques
- 7:11Memory encryption limits
- 8:38Access protection and IO issues
- 10:24CPU state protection
- 12:30Booting secure VMs
- 13:35Secure IO and swap
- 14:42Collaborative development efforts
- 16:47Testing secure VMs
- 17:56Future of secure VM migration
- 19:45Secure IO devices
- 20:48VM dumping protections
- 22:37Summary
related talks
18mSecurely booting confidential VMs with encrypting disk
19mSupporting Trusted Virtual Machines with Hardware-based Secure Remote Memory
13mVM Security with Confidential Computing
44mAdvancements in Confidential Computing
36mConfidential VMs in the cloud
44mAMD x86 Memory Encryption Technologies
41mConfidential Computing, from host to workload
20mEncrypted Virtual Machine Images for Confidential Computing