more clarification on deps

srl-labs · Jul 17, 2021 · 0372566 · 0372566
1 parent 70d5a22
commit 0372566
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/docs/manual/kinds/cvx.md b/docs/manual/kinds/cvx.md
@@ -15,7 +15,9 @@ CVX supports two modes of operation:
 * Using only the container runtime -- this mode runs Cumulus VX container image directly inside the container runtime (e.g. Docker). Due to the lack of Cumulus VX kernel modules, some features are not supported, most notable one being MLAG. In order to use this mode add `runtime: docker` under the cvx node definition (see also [this example](https://github.com/srl-labs/containerlab/blob/master/lab-examples/cvx02/topo.clab.yml)).
 
 !!! note
-    When running in the default `ignite` runtime mode, the only host OS dependency is `/dev/kvm` required to support harware-assisted virtualisation. Firecracker VMs are spun up inside a special "sandbox" container that has all the right tools and dependencies required to run micro-VMs. Additionally, containerlab creates a number of directories under `/var/lib/firecracker` for nodes running in `ignite` runtime to store runtime metadata; these directories are managed by containerlab.
+    When running in the default `ignite` runtime mode, the only host OS dependency is `/dev/kvm`[^1] required to support harware-assisted virtualisation. Firecracker VMs are spun up inside a special "sandbox" container that has all the right tools and dependencies required to run micro-VMs.
+
+    Additionally, containerlab creates a number of directories under `/var/lib/firecracker` for nodes running in `ignite` runtime to store runtime metadata; these directories are managed by containerlab.
 
 ## Managing cvx nodes
 Cumulus VX node launched with containerlab can be managed via the following interfaces:
@@ -71,4 +73,6 @@ The following labs feature CVX node:
 
 ## Known issues or limitations
 
-* CVX in Ignite is always attached to the default docker bridge network
+* CVX in Ignite is always attached to the default docker bridge network
+
+[^1]: this device is already part of the linux kernel, therefore this can be read as "no external dependencies are needed for running cvx with `ignite` runtime.