KVM not available

Open
#2,248 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
docker, linux

Research direction

The report is a user's host setup failure rather than a named code change: the container logs say /dev/kvm is missing even though the run command passes --device=/dev/kvm. Start by checking the reporter's host for /dev/kvm and the Docker run flags, then read the two existing comments for any diagnosis. Done means a documented cause or a reply that resolves the setup, not a code change.

Written by the indexing model from the issue text.

Description

Operating system

Zorin 18.1

Description

❯ ERROR: KVM acceleration is not available (/dev/kvm is missing), this will cause the machine to run about 10 times slower.
❯ ERROR: See the FAQ for possible causes, or disable acceleration by adding the "KVM=N" variable (not recommended).

Docker compose
docker run -it --rm --privileged --name windows -e "VERSION=11" -p 8006:8006 --device=/dev/kvm --device=/dev/net/tun --cap-add NET_ADMIN -v "${PWD:-.}/windows:/storage" --stop-timeout 120 docker.io/dockurr/windows
Docker log
❯ Starting Windows for Docker v6.06...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Core i5 1335U | RAM: 3/4 GB | DISK: 421 GB (/0x6a656a63) | KERNEL: 7.0.14-linuxkit

❯ ERROR: KVM acceleration is not available (/dev/kvm is missing), this will cause the machine to run about 10 times slower.
❯ ERROR: See the FAQ for possible causes, or disable acceleration by adding the "KVM=N" variable (not recommended).
Screenshots (optional)

No response

Dominant language
Shell
Stars
54.2k
Forks
5.2k
PR merge metrics
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dockur/windows

All issues in dockur/windows

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.