The emulator process for AVD was killed 🤖 Android

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.

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:

🧠 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.