microsoft / microsoft/OmniParser
ERROR: KVM acceleration not available (device file missing)
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 25.4k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
I install everything in Linux with Ubuntu 22.04.5 LTS.
I followed this setup guideline: https://github.com/microsoft/OmniParser/tree/master/omnitool
after running ./manage_vm.sh create
it successfully built docker image: windows-local and run a docker container: omni-windows
but after several minutes, docker container existed.
after checking the docker container log. There is error "ERROR: KVM acceleration not available (device file missing), this will cause a major loss of performance"
below is the docker container log.
❯ Starting OmniParser Windows for Docker v0.00...
❯ For support visit https://github.com/microsoft/OmniParser
❯ CPU: AMD EPYC 7V13 64 Core | RAM: 197/217 GB | DISK: 171 GB (ext4) | KERNEL: 5.15.0-1061-azure...
❯ Extracting local ISO image...
❯ Detecting version from ISO image...
❯ Detected: Windows 11 Enterprise (Evaluation)
❯ Adding drivers to image...
❯ Adding OEM folder to image...
❯ Adding win11x64-enterprise-eval.xml for automatic installation...
❯ Building Windows 11 image...
❯ Creating a 20G growable disk image in raw format...
❯ ERROR: KVM acceleration not available (device file missing), this will cause a major loss of performance.
❯ ERROR: See the FAQ on how to diagnose the cause, or continue without KVM by setting KVM=N (not recommended).
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the omnitool setup guideline and the manage_vm.sh create entry point, then inspect the reported Docker container log on Ubuntu 22.04.5 LTS. Check the FAQ referenced in the log for the expected KVM prerequisites and supported environment. Done means the documented setup either provides KVM acceleration or clearly reports the supported fallback behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, ubuntu
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100