Skip to content
This repository was archived by the owner on May 3, 2022. It is now read-only.

Commit 10612fd

Browse files
mayankkumar2Nick Vidal
authored and
Nick Vidal
committed
docs(kvm): kvm usage while running enarx
Signed-off-by: Mayank Kumar <mayank22oct@gmail.com>
1 parent 446a911 commit 10612fd

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

docs/Installation/Wasm.md

+11
Original file line numberDiff line numberDiff line change
@@ -36,3 +36,14 @@ setting the `ENARX_BACKEND` environment variable:
3636

3737
$ enarx run --backend=sgx target/wasm32-wasi/release/hello-world.wasm
3838
$ ENARX_BACKEND=sgx enarx run target/wasm32-wasi/release/hello-world.wasm
39+
40+
#### Note about KVM backend
41+
42+
`enarx` will look for the kvm driver loaded by the kernel and will be ready to use if it's found. Linux kernel
43+
automatically loads the kvm module if the virtualization feature is enabled by the hardware. The status of whether or not
44+
enarx was able to find the driver can be checked with the command `enarx info`. If the output shows the driver for kvm is available, you are ready to use enarx using kvm backend.
45+
46+
When you execute the `enarx run` command, enarx tries to automatically select the appropriate driver, and kvm is automatically selected if it's the only backend available. But if you want to specifically use the kvm backend you can pass the `kvm` as a parameter to `--backend` option, or set the `ENARX_BACKEND` environment variable as `kvm`:
47+
48+
$ enarx run --backend=kvm target/wasm32-wasi/release/hello-world.wasm
49+
$ ENARX_BACKEND=kvm enarx run target/wasm32-wasi/release/hello-world.wasm

0 commit comments

Comments
 (0)