diff options
| author | Jesse Larrew <jlarrew@users.noreply.github.com> | 2018-12-13 04:50:22 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-12-13 04:50:22 -0600 |
| commit | 990f36d9fe3826b0b12b9bd2d3ce3c2124d19adc (patch) | |
| tree | 4e7713f62a03079fb04908d4a961fed62e11ec3e | |
| parent | d0a76c8948ba80c2cb47f1c62b1f1633ba50ec64 (diff) | |
| download | cachepc-amdsev-990f36d9fe3826b0b12b9bd2d3ce3c2124d19adc.tar.gz cachepc-amdsev-990f36d9fe3826b0b12b9bd2d3ce3c2124d19adc.zip | |
Update README.md for SEV Containers
Update README.md to include information about the SEV container proof-of-concept code on the 'kata' branch.
| -rw-r--r-- | README.md | 10 |
1 files changed, 9 insertions, 1 deletions
@@ -15,6 +15,7 @@ * [ openSuse-Tumbleweed](#tumbleweed) * [ Prepare Host OS ](#tumbleweed-host) * [ Launch SEV VM ](#tumbleweed-launch-vm) +* [ SEV Containers ](#kata) * [ Additional resources ](#resources) * [ FAQ ](#faq) * [ How do I know if Hypervisor supports SEV ](#faq-1) @@ -312,7 +313,14 @@ Since virt-manager does not support SEV yet hence we need to use 'virsh' command <soft_limit unit='G'>5</soft_limit> </memtune> ``` - + +<a name="kata"></a> +## SEV Containers + +Container runtimes that use hardware virtualization to further isolate container workloads can also make use of SEV. As a proof-of-concept, the [kata](https://github.com/AMDESE/AMDSEV/tree/kata) branch contains an SEV-capable version of the Kata Containers runtime that will start all containers inside of SEV virtual machines. + +For installation instructions on Ubuntu systems, see the [README](https://github.com/AMDESE/AMDSEV/blob/kata/README.md). + <a name="resources"></a> # Additional Resources |