diff options
| author | Dorjoy Chowdhury <dorjoychy111@gmail.com> | 2024-11-09 18:28:44 +0600 |
|---|---|---|
| committer | Philippe Mathieu-Daudé <philmd@linaro.org> | 2024-12-13 15:26:58 +0100 |
| commit | 44d9fab1f8a1d376741ff4505ec39f7f0a729ab2 (patch) | |
| tree | b821ba5fa761921390bd1b45f7c3c2a2d488f688 /docs/system | |
| parent | 83aaec1d5a49f158abaa31797a0f976b3c07e5ca (diff) | |
| download | qemu-44d9fab1f8a1d376741ff4505ec39f7f0a729ab2.zip qemu-44d9fab1f8a1d376741ff4505ec39f7f0a729ab2.tar.gz qemu-44d9fab1f8a1d376741ff4505ec39f7f0a729ab2.tar.bz2 | |
docs/nitro-enclave: Fix terminal commands formatting
Signed-off-by: Dorjoy Chowdhury <dorjoychy111@gmail.com>
Reviewed-by: Alexander Graf <graf@amazon.com>
Message-ID: <20241109122844.24057-1-dorjoychy111@gmail.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Diffstat (limited to 'docs/system')
| -rw-r--r-- | docs/system/i386/nitro-enclave.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/system/i386/nitro-enclave.rst b/docs/system/i386/nitro-enclave.rst index 73e3ede..48eda5b 100644 --- a/docs/system/i386/nitro-enclave.rst +++ b/docs/system/i386/nitro-enclave.rst @@ -48,13 +48,13 @@ Running a nitro-enclave VM First, run `vhost-device-vsock`__ (or a similar tool that supports vhost-user-vsock). The forward-cid option below with value 1 forwards all connections from the enclave VM to the host machine and the forward-listen (port numbers separated by '+') is used -for forwarding connections from the host machine to the enclave VM. - -__ https://github.com/rust-vmm/vhost-device/tree/main/vhost-device-vsock#using-the-vsock-backend +for forwarding connections from the host machine to the enclave VM:: $ vhost-device-vsock \ --vm guest-cid=4,forward-cid=1,forward-listen=9001+9002,socket=/tmp/vhost4.socket +__ https://github.com/rust-vmm/vhost-device/tree/main/vhost-device-vsock#using-the-vsock-backend + Now run the necessary applications on the host machine so that the nitro-enclave VM applications' vsock communication works. For example, the nitro-enclave VM's init process connects to CID 3 and sends a single byte hello heartbeat (0xB7) to let the @@ -65,7 +65,7 @@ the applications on the host machine that would typically be running in the pare VM for successful communication with the enclave VM. Then run the nitro-enclave VM using the following command where ``hello.eif`` is -an EIF file you would use to spawn a real AWS nitro enclave virtual machine: +an EIF file you would use to spawn a real AWS nitro enclave virtual machine:: $ qemu-system-x86_64 -M nitro-enclave,vsock=c,id=hello-world \ -kernel hello-world.eif -nographic -m 4G --enable-kvm -cpu host \ |