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

**Code:** `The emulator process for AVD was killed` · **Category:** Android · **Seen on:** Android

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

## 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

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/android/emulator-process-killed)