The emulator process for AVD was killed Android Origin: On your device Last updated 12 Oct 2026

Android Emulator: The emulator process for AVD x has terminated / was killed (hypervisor not available)

The Android Emulator crashed or couldn’t start — usually missing hardware acceleration, low disk/RAM, or GPU driver problems.

Exact message you may see The emulator process for AVD was killedhas terminatedx86 emulation currently requires hardware accelerationHAXM is not installedKVM is required
Explore the map of this error Full error map →
Seen on: Android

Meaning

The emulator needs a hypervisor (WHPX/AEHD on Windows, Hypervisor.framework on macOS, KVM on Linux), enough free disk for the AVD and working graphics. Running inside a VM without nested virtualization fails.

Common causes

  • Hardware acceleration not installed/enabled (WHPX/AEHD/KVM)
  • Virtualization disabled in BIOS
  • Low disk space for the AVD
  • GPU driver issues (switch to software rendering)
  • Conflicting hypervisors (VirtualBox, older HAXM)

⚡ Quick fix

  1. Enable virtualization in BIOS and install the hypervisor driver
  2. Free disk space; wipe/cold boot the AVD
  3. Set Graphics to Software in AVD settings

Detailed fix by platform

Shell

  1. kotlin
    $ANDROID_HOME/emulator/emulator -accel-check
$ANDROID_HOME/emulator/emulator -avd Pixel_8_API_35 -gpu swiftshader_indirect -no-snapshot-load

How to diagnose

  1. Accel — emulator -accel-check output
  2. Disk — Free space
  3. Logs — Idea log / emulator stdout

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

0x80370102 — WslRegisterDistribution failed with error: 0x80370102 (virtual machine could not be started) (Windows)0x80370102ActivityNotFoundException — ActivityNotFoundException: Unable to find explicit activity class; have you declared this activity in your AndroidManifest.xml? (Android)ActivityNotFoundExcep…adb unauthorized — adb: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set (Android)adb unauthorizedAndroid resource linking failed — AAPT: error: resource x (aka y) not found — Android resource linking failed (Android)Android resource link…android:attr/lStar not found — AAPT: error: resource android:attr/lStar not found (Android)android:attr/lStar no…INSTALL_FAILED_INSUFFICIENT_STORAGE — INSTALL_FAILED_INSUFFICIENT_STORAGE: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE] (Android)INSTALL_FAILED_INSUFF…no devices/emulators found — adb: no devices/emulators found / error: device not found (Android)no devices/emulators …WSL 2 installation is incomplete — Docker Desktop: WSL 2 installation is incomplete / WSL update required (Docker)WSL 2 installation is…The emula…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.