The Android Emulator says /dev/kvm is not found
/dev/kvm is not foundShort answer
The emulator wants a hypervisor and cannot find one. Run the emulator's own -accel-check first. On Linux the usual causes are KVM not installed or virtualization switched off in the BIOS. On macOS there is no KVM at all, and inside another virtual machine the emulator cannot run accelerated.
Fix it fast
1Find out which cause you have
Ask the emulator which hypervisor it can use. Replace the path with your SDK location. The answer differs per operating system, which tells you which cause below applies.
$ANDROID_HOME/emulator/emulator -accel-check2Match what you see, then jump to its fix
- 1
-accel-check mentions Hypervisor.Framework, or a guide you followed tells you to install KVM or HAXMYou are on macOS, where KVM does not existFix - 2
kvm-ok says /dev/kvm does not exist, or the package is not foundKVM is not installed on LinuxFix - 3
The CPU lists vmx or svm, but /dev/kvm still does not appearVirtualization is switched off in the BIOS or UEFIFix - 4
Linux runs under VirtualBox, VMware, Docker or a cloud instance that does not expose virtualizationYou are running the emulator inside another virtual machineFix
- 1
What does the error look like?
/dev/kvm is not foundKVM acceleration can NOT be usedINFO: Your CPU does not support KVM extensions
Cause 1 of 4
You are on macOS, where KVM does not exist
1Check
On macOS the emulator uses Apple's built-in Hypervisor.Framework. Intel HAXM is no longer supported there since macOS 11. A message about /dev/kvm on a Mac usually comes from an old guide or a copied config.
sw_vers -productVersion
$ANDROID_HOME/emulator/emulator -accel-check2Fix
Install nothing. Update the Android Emulator in the SDK Manager and use a system image that matches your chip: arm64-v8a on Apple silicon, x86_64 on an Intel Mac.
$ANDROID_HOME/emulator/emulator -list-avds3Verify
-accel-check prints a line naming the Hypervisor.Framework.
$ANDROID_HOME/emulator/emulator -accel-checkConfirmed by developer.android.com
Cause 2 of 4
KVM is not installed on Linux
1Check
Install cpu-checker and check two things: whether the CPU lists virtualization flags and whether kvm-ok reports that acceleration can be used. An output of 0 from the egrep means the CPU has no hardware virtualization.
sudo apt-get install cpu-checker
egrep -c '(vmx|svm)' /proc/cpuinfo
sudo kvm-ok2Fix
Install the KVM packages. The command below is the one for Ubuntu 18.10 and later.
sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils3Verify
kvm-ok prints INFO: /dev/kvm exists and KVM acceleration can be used.
sudo kvm-okConfirmed by developer.android.com
Cause 3 of 4
Virtualization is switched off in the BIOS or UEFI
1Check
On PCs the virtualization extensions are often off by default. Intel calls the setting VT-x and AMD calls it AMD-V or SVM. The egrep count above is 1 or more when the CPU supports it.
egrep -c '(vmx|svm)' /proc/cpuinfo2Fix
Enter the BIOS or UEFI setup, turn on the virtualization option for your CPU, save and boot again. The menu name depends on the vendor, so use the system vendor's documentation.
sudo kvm-ok3Verify
After the reboot, kvm-ok reports that KVM acceleration can be used.
sudo kvm-okConfirmed by developer.android.com
Cause 4 of 4
You are running the emulator inside another virtual machine
1Check
A VM-accelerated emulator cannot run inside another VM such as one hosted by VirtualBox, VMware or Docker. It has to run directly on the host computer.
systemd-detect-virt
sudo kvm-ok2Fix
Run the emulator on the host machine instead, or test on a physical device connected over adb.
adb devices3Verify
The emulator starts on the host, or the physical device shows up as device in the list.
adb devicesConfirmed by developer.android.com
How do I stop it coming back?
- Pick system images that match the CPU: x86_64 images on Intel or AMD, arm64-v8a on Apple silicon.
- Do not follow HAXM or KVM guides on macOS; use the emulator's own -accel-check to see what it will use.
- Keep the Android Emulator package updated in the SDK Manager.
- On Linux build servers, use a host that exposes virtualization, or run tests on real devices.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fixMobile apps
The emulator says the GPU driver is unsupported and falls back to software
vulkan-1.dll cannot be found
The emulator picks a graphics mode when it starts.
4 causes, each with a fixMobile apps
The Android Emulator will not start with hardware acceleration (HAXM, Hyper-V, KVM)
KVM acceleration can NOT be used
Intel HAXM is discontinued, and current emulators no longer use it.
4 causes, each with a fix