Update notes on nested virt

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>

Author: alexellis

docs/examples/kvm-guest.md

@@ -1,44 +1,15 @@
 # Example: Run a KVM guest
 
-It is possible to launch a Virtual Machine (VM) within a GitHub Action. Support for virtualization is not enabled by default for Actuated. The Agent has to be configured to use a custom kernel.
+It is possible to launch a Virtual Machine (VM) within a GitHub Action using nested virtualisation.
 
-There are some prerequisites to enable KVM support:
+With the following caveats:
 
-- `aarch64` runners are not supported at the moment.
-- A bare-metal host for the Agent is required.
+- Nested Virtualisation is generally slower than bare-metal.
+- Arm is not supported by the Linux Kernel or the current generation of Arm SoCs.
 
+The `kvm` and `kvm_intel` / `kvm_amd` modules are shipped with the actuated Kernel, so you can load them in your workflow via `sudo modprobe`.
 
-!!! info "Nested virtualisation is a premium feature"
-    This feature requires a plan size of 15 concurrent builds or greater, however you can get a 14-day free trial by contacting our team directly through the actuated Slack.
-
-## Configure the Agent
-
-1. Make sure [nested virtualization is enabled](https://ostechnix.com/how-to-enable-nested-virtualization-in-kvm-in-linux/) on the Agent host.
-
-2. Edit `/etc/default/actuated` on the Actuated Agent and add the `kvm` suffix to the `AGENT_KERNEL_REF` variable:
-
-    ```diff
-    - AGENT_KERNEL_REF="ghcr.io/openfaasltd/actuated-kernel:x86_64-latest"
-    + AGENT_KERNEL_REF="ghcr.io/openfaasltd/actuated-kernel:x86_64-kvm-latest"
-    ```
-
-3. Also add it to the `AGENT_IMAGE_REF` line:
-
-    ```diff
-    - AGENT_IMAGE_REF="ghcr.io/openfaasltd/actuated-ubuntu22.04:x86_64-latest"
-    + AGENT_IMAGE_REF="ghcr.io/openfaasltd/actuated-ubuntu22.04:x86_64-kvm-latest"
-    ```
-
-3. Restart the Agent to use the new kernel.
-
-    ```bash
-    sudo systemctl daemon-reload && \
-        sudo systemctl restart actuated
-    ```
-
-4. Run a [test build](/test-build/) to verify KVM support is enabled in the runner. The specs script from the test build will report whether `/dev/kvm` is available.
-
-## Run a Firecracker microVM
+## Example: Run a Firecracker microVM
 
 This example is an adaptation of the [Firecracker quickstart guide](https://github.com/firecracker-microvm/firecracker/blob/main/docs/getting-started.md) that we run from within a GitHub Actions workflow.
 

docs/faq.md

@@ -348,9 +348,7 @@ It is possible to launch a Virtual Machine (VM) with KVM from within a Firecrack
 
 Use-cases may include: building and snapshotting VM images, running Packer, launching VirtualBox and Vagrant, accelerating the Android emulator, building packages for NixOS and other testing which requires KVM.
 
-It's disabled by default, but you can opt-in to the feature by following the steps in this article:
-
-[How to run a KVM guest in your GitHub Actions](https://actuated.com/blog/kvm-in-github-actions)
+Follow an example build that uses Firecracker within a GitHub Action: [How to run a KVM guest in your GitHub Actions](https://actuated.com/blog/kvm-in-github-actions)
 
 At time of writing, only Intel and AMD CPUs support nested virtualisation.