From 0caf956e170f59f299ddf562842963c236b1f42b Mon Sep 17 00:00:00 2001 From: Kroese Date: Tue, 11 Jun 2024 19:53:10 +0200 Subject: [PATCH] docs: KVM information (#110) --- readme.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/readme.md b/readme.md index 8d5948b..b0a9e0a 100644 --- a/readme.md +++ b/readme.md @@ -146,9 +146,17 @@ kubectl apply -f kubernetes.yml sudo kvm-ok ``` - If you receive an error from `kvm-ok` indicating that KVM acceleration can't be used, check whether virtualization extensions are enabled in your BIOS. If you are running the container inside a VM instead of directly on the host, you will also need to enable nested virtualization in its settings. If you are using a cloud provider, you may be out of luck as most of them do not allow nested virtualization for their VPS's. If you are using MacOS, you are also out of luck, as only Linux and Windows support KVM. + If you receive an error from `kvm-ok` indicating that KVM acceleration can't be used, please check whether: - If you don't receive any error from `kvm-ok` at all, but the container still complains that `/dev/kvm` is missing, it might help to add `privileged: true` to your compose file (or `--privileged` to your `run` command), to rule out any permission issue. + - the virtualization extensions (`Intel VT-x` or `AMD SVM`) are enabled in your BIOS. + + - you are running an operating system that supports them, like Linux or Windows 11 (macOS and Windows 10 do not unfortunately). + + - you enabled "nested virtualization" if you are running the container inside a virtual machine. + + - you are not using a cloud provider, as most of them do not allow nested virtualization for their VPS's. + + If you didn't receive any error from `kvm-ok` at all, but the container still complains that `/dev/kvm` is missing, it might help to add `privileged: true` to your compose file (or `--privileged` to your `run` command), to rule out any permission issue. * ### How do I assign an individual IP address to the container?