External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-11-05 11:31:14 +00:00
Code Issues Packages Projects Releases Wiki Activity
e6208d1c0e
cloud-hypervisor/docs/intel_sgx.md
Sebastien Boeuf e6e58e6d66 docs: Replace Cloud-Hypervisor with Cloud Hypervisor syntax 
The proper way to refer to the project is "Cloud Hypervisor" without the
hyphen in the middle. On the other hand, if one refers to the binary
name, it is "cloud-hypervisor".

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-11-15 17:27:23 +01:00

2.4 KiB
Raw Blame History

Intel SGX

Intel® Software Guard Extensions (Intel® SGX) is an Intel technology designed to increase the security of application code and data. Cloud Hypervisor supports SGX virtualization through KVM. Because SGX is built on hardware features that cannot be emulated in software, virtualizing SGX requires support in KVM and in the host kernel. The required Linux and KVM changes can be found in the KVM SGX Tree.

Utilizing SGX in the guest requires a kernel/OS with SGX support, e.g. a kernel built using the SGX Linux Development Tree or the KVM SGX Tree. Running KVM SGX as the guest kernel allows nested virtualization of SGX.

For more information about SGX, please refer to the SGX Homepage.

For more information about SGX SDK and how to test SGX, please refer to the following instructions.

Cloud Hypervisor support

Assuming the host exposes /dev/sgx_vepc, we can pass SGX enclaves through the guest.

In order to use SGX enclaves within a Cloud Hypervisor VM, we must define one or several Enclave Page Cache (EPC) sections. Here is an example of a VM being created with 2 EPC sections, the first one being 64MiB with pre-allocated memory, the second one being 32MiB with no pre-allocated memory.

./cloud-hypervisor \
    --cpus boot=1 \
    --memory size=1G \
    --disk path=focal-server-cloudimg-amd64.raw \
    --kernel vmlinux \
    --cmdline "console=ttyS0 console=hvc0 root=/dev/vda1 rw" \
    --sgx-epc id=epc0,size=64M,prefault=on id=epc1,size=32M,prefault=off

Once booted, and assuming your guest kernel contains the patches from the KVM SGX Tree, you can validate SGX devices have been correctly created under /dev/sgx:

ls /dev/sgx*
/dev/sgx_enclave  /dev/sgx_provision  /dev/sgx_vepc

From this point, it is possible to run any SGX application from the guest, as it will access /dev/sgx_enclave device to create dedicated SGX enclaves.

Note: There is only one contiguous SGX EPC region, which contains all SGX EPC sections. This region is exposed through ACPI and marked as reserved through the e820 table. It is treated as yet another device, which means it should appear at the end of the guest address space.