Troubleshooting

The problems here split by where they come from. The first is your machine’s, and it applies however you got the binary. The rest are the source tree’s, and they only reach you because the sandbox is pre-release and you built it yourself.

On your machine

/dev/kvm permission denied

On Linux, the sandbox needs a hypervisor that answers, and /dev/kvm must be readable and writable by your user. This usually means adding yourself to the kvm group:

sudo usermod -aG kvm $USER

You may need to sign out and back in for the change to take effect. This is a host permission rather than anything the sandbox installs, so no rebuild and no reinstall fixes it. Linux support covers what else the host provides.

When you build from source

The sandbox is pre-release and Quickstart builds it from its source tree, so everybody running it today is building it. Both problems below need cargo and the repository to fix — neither is something a packaged application would hand you.

The Tormoni book is the authority on that tree, and it changes without notice while the sandbox is pre-v0.1.0 — believe it over this page.

Process killed on macOS

If macOS kills the tormoni process on launch, it likely lacks the com.apple.security.hypervisor entitlement. Re-sign the binary after building:

cargo xtask sign

A signature does not reliably outlive the next cargo build, so this is a step of the build rather than a one-time repair. macOS support has the rest of the signing and bundling story.

Missing libkrun

If the application fails to start with errors about missing shared libraries, install libkrun through your system package manager. It is a C library carrying a kernel payload, so Cargo neither builds nor downloads it, and no amount of rebuilding the Rust tree produces it.