KVM not available
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
- Domain
- infrastructure
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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dockur/windows
-
[Bug]: QEMU segfaults in spice_server_destroy on guest shutdown when a SPICE client is connectedOpenbug
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
[Feature]: SelkiesOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 3/5 Half a day Newbie friendliness 20/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 43/100
-
question
Difficulty 5/5 Over a week Newbie friendliness 8/100
Similar issues
-
application-issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Installomator/Installomator#3657 · 1 comment ·
Maintainers usually reply within 3 days
-
Own-agent checks: reject the Actions bot id in admit.mjs and test the source label in pr-verifyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melodic-software/claude-code-plugins#17374 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
out-of-date
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
CachyOS/CachyOS-PKGBUILDS#2154 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
eip-work/kuboard-press#723 ·