From 3fd6305d64aa10ffa65ca3620ccf0924a14c1cb3 Mon Sep 17 00:00:00 2001 From: biswaroop1547 Date: Fri, 6 Nov 2026 13:55:26 +0530 Subject: [PATCH 1/2] docs: check KVM the way the Linux service uses it The old check tested file modes, so it printed 'KVM access is ready' for a device node without a working KVM driver, and for a login that has the kvm group while the user's service manager still has the old groups. Open the device through the user's systemd manager instead, and say that a group change needs a restart when another session or lingering keeps services running. Co-Authored-By: Claude Opus 5.5 --- content/docs/workspaces/setup.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/workspaces/setup.mdx b/content/docs/workspaces/setup.mdx index ddb9280..f62b035 100644 --- a/content/docs/workspaces/setup.mdx +++ b/content/docs/workspaces/setup.mdx @@ -80,13 +80,13 @@ Use **64-bit glibc Linux with systemd**: Ubuntu 24.04, Debian 13, or newer. The The host needs **KVM**, Linux's hardware virtualization facility. A virtual machine also needs nested virtualization from its host provider. -**Check access to KVM.** Run this on the Linux machine: +**Check access to KVM.** Run this on the Linux machine as the workspace owner. It opens KVM the way the background service will: ```bash -test -r /dev/kvm && test -w /dev/kvm && echo 'KVM access is ready' +systemd-run --user --wait --pipe --quiet sh -c 'test -c /dev/kvm && : <> /dev/kvm' && echo 'KVM access is ready' ``` -If it does not print `KVM access is ready`, stop here. Ask your administrator to enable KVM and grant your user read/write access. After a group-permission change, sign out and sign in again. +If it does not print `KVM access is ready`, stop here. Ask your administrator to enable KVM and grant your user read/write access, usually through the `kvm` group. After a group change, restart the machine. Signing out is not enough while another session or lingering keeps your background services running. A Raspberry Pi needs a supported 64-bit operating system and kernel with usable KVM. An ARM64 processor alone is not enough. Send your system details and KVM check to support if you are unsure. From 89b30123bd659d66ef016d012cc7f5b3deb063ba Mon Sep 17 00:00:00 2001 From: biswaroop1547 Date: Fri, 6 Nov 2026 15:47:48 +0530 Subject: [PATCH 2/2] docs: run the KVM check as a one-shot unit systemd-run --wait/--pipe needs the user D-Bus, so the check said "not ready" on a working host without one. A one-shot unit reaches the user manager without it, like the daemon's own setup check. Co-Authored-By: Claude Opus 5.5 --- content/docs/workspaces/setup.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/workspaces/setup.mdx b/content/docs/workspaces/setup.mdx index f62b035..2fc63ea 100644 --- a/content/docs/workspaces/setup.mdx +++ b/content/docs/workspaces/setup.mdx @@ -83,7 +83,7 @@ The host needs **KVM**, Linux's hardware virtualization facility. A virtual mach **Check access to KVM.** Run this on the Linux machine as the workspace owner. It opens KVM the way the background service will: ```bash -systemd-run --user --wait --pipe --quiet sh -c 'test -c /dev/kvm && : <> /dev/kvm' && echo 'KVM access is ready' +systemd-run --user --quiet --collect -p Type=oneshot sh -c 'test -c /dev/kvm && : <> /dev/kvm' && echo 'KVM access is ready' ``` If it does not print `KVM access is ready`, stop here. Ask your administrator to enable KVM and grant your user read/write access, usually through the `kvm` group. After a group change, restart the machine. Signing out is not enough while another session or lingering keeps your background services running.