No accelerator found - failed to create HAX VM

emulator: qemu-system-x86_64: failed to initialize hax: operation not supported by device
intel haxm
haxm 6.2 1 download
hamx
android emulator fails to start
qemu-system-i386.exe failed to initialize hax: invalid argument
what is haxm 6.2 1

I am unable to launch any emulators on Android Studio. When trying to launch an emulator, I get the following error:

Failed to create vm ffffffff
Failed to create HAX VM
No accelerator found.
failed to initialize HAX: Invalid argument
Hax is enabled
Hax ram_size 0x80000000`

I have uninstalled Intel HAXM, installed it again, restarted Android studio, tried different system images, and tweaked heap space for the emulator. I have tried different device images, different API levels, and have tried switching emulated performance from auto to both hardware and software to no avail. Nothing I have tried has worked. Here are my emulator's details:

Name: Nexus_6P_API_23
CPU/ABI: Google APIs Intel Atom (x86)
Path: /Users/mobile/.android/avd/Nexus_6P_API_23.avd
Target: google_apis [Google APIs] (API level 23)
Skin: nexus_6p
SD Card: /Users/mobile/.android/avd/Nexus_6P_API_23.avd/sdcard.img
hw.lcd.density: 560
hw.dPad: no
avd.ini.encoding: UTF-8
hw.camera.back: none
disk.dataPartition.size: 800M
hw.gpu.enabled: yes
runtime.network.latency: none
hw.keyboard: yes
runtime.network.speed: full
hw.device.hash2: MD5:9b564b60b1aebee32c73ded9daa1e620
hw.ramSize: 2048
tag.id: google_apis
tag.display: Google APIs
hw.sdCard: yes
hw.device.manufacturer: Google
hw.mainKeys: no
hw.accelerometer: yes
hw.trackBall: no
hw.device.name: Nexus 6P
hw.sensors.proximity: yes
hw.gpu.mode: auto
hw.battery: yes
AvdId: Nexus_6P_API_23
image.sysdir.1: system-images/android-23/google_apis/x86/
hw.sensors.orientation: yes
hw.audioInput: yes
hw.camera.front: none
hw.gps: yes
avd.ini.displayname: Nexus 6P API 23
vm.heapSize: 1028
image.androidVersion.api: 23
runtime.scalefactor: auto

Following instructions from Intel's docs, I ran the command kextstat | grep intel to verify the HAXM installation and got the following return:

154 0 0xffffff7f82ae4000 0x14000 0x14000 com.intel.kext.intelhaxm (6.0.3) <7 5 4 3 1>

Try installing or updating Intel Emulator Accelerator (HAXM installer) from SDK Manager and also check if Intel VT-x is enabled in your BIOS settings

"Failed to create HAX VM" · Issue #107 · intel/haxm · GitHub, Hi guys, i am beginner in using Haxm. I am using android studio, when i try to launch emulator, its look like intelHaxm is not working properly. Unfortunately, when trying to create the HAXM VM device node, emulator stores the path name (\\.\hax_vm00) in an ANSI string, and passes it to CreateFile. In effect, it calls CreateFileA instead of CreateFileW. Here's what I think happens next: Windows implements CreateFileA as a wrapper around CreateFileW. Therefore, the first thing it does is convert the path name from ANSI to Unicode.

Android Emulator fails to execute and doesn't start, Failed to open vm 4. Failed to create HAX VM No accelerator found. failed to initialize HAX: Invalid argument. Hax is enabled. Hax ram_size  Failed to create HAX VM No accelerator found. qemu-system-x86_64.exe: failed to initialize HAX: Invalid argument. I have 16 GB of ram memory in my PC. I try to change

Try to uninstall "Intel x86 Emulator Accelerator (HAXM installer)" from Android SDK manager, than install it again. That helped for me.

No accelerator found - failed to create HAX VM, No accelerator found - failed to create HAX VM. 13:56 Executing tasks: [:app:​assembleDebug] 13:56 Emulator: Incompatible HAX module version 3,requires  And this isn't about the VM (guest), if I even just try to run, > "c:\Program Files\qemu\qemu-system-x86_64.exe" -accel hax Basically, just get a window to open, with acceleration enabled I get, Open the vm device error:/dev/hax_vm/vm00, ec:3 Failed to open vm 0 Failed to create HAX VM No accelerator found.

VT-x is enabled by default in all Macs these days.

If you are running Parallels at the same time this will cause the above error. I'm suspect it worked when you rebooted due to Parallels not being run in the background.

Android emulators stopped working on macOS 10.13 (High Sierra , Non of them started and logs showed something like: Failed to open vm 3 Failed to create HAX VM No accelerator found. failed to initialize  1. Select the AVD that is not launching 2. Click "Start" on the right 3. In the launch options window that opens, select the option to Wipe user data. 4. Click "Launch" If you do not have the CUI Google Emulator Manager then you either have to switch to using the Android SDK Tools version <= 25.2.5.

Solution A:

Open SDK MAnager.Install HAX Installer and Android Emulator :

Follow the pic:

Solution B:

Restart your pc and go to BIOS Setting. Enable VT-x or Virtualization or Virtualization Technology from your Advance BIOS setting.

Solution C:

Open your SDK folder and follow the path(android-sdk-windows\extras\intel\Hardware_Accelerated_Execution_Manager). and double click to intelhaxm-android.exe for update the software.

Or follow those pic:

android-sdk-windows\

extras\

intel\

Hardware_Accelerated_Execution_Manager

Double Click intelhaxm-android.exe

Bug #1871250 “Failed to create HAX VM” : Bugs : QEMU, I get, Open the vm device error:/dev/hax_vm/vm00, ec:3 Failed to open vm 0 Failed to create HAX VM No accelerator found. But I checked - I  [Bug 1871250] [NEW] Failed to create HAX VM Russell Morris Re: [Bug 1871250] Failed to create HAX VM Volker Rümelin RE: [Bug 1871250] Failed to create HAX VM Morris, Russell

13:56 Executing tasks: [:app:assembleDebug] 13:56 Emulator: Incompatible HAX module version 3,requires minimum version 4 13:56  To feel the difference made by HAXM acceleration, shut down the VM, and relaunch it without -accel hax: qemu-system-x86_64.exe -hda X:\path\to\debian_wheezy_amd64_standard.qcow2 If you’re still not impressed, try a more sophisticated VM image such as debian_wheezy_amd64_desktop.qcow2 , which boots to a desktop environment.

1 2 3 4 5 6 7 8 9 10, 13:56 Executing tasks: [:app:assembleDebug] 13:56 Emulator: Incompatible HAX module version 3,requires minimum  If STATE is not set to RUNNING, then HAXM is not installed. If your computer can support HAXM but HAXM is not installed, use the steps in the next section to install HAXM. Installing HAXM. HAXM install packages for Windows are available from the Intel Hardware Accelerated Execution Manager page. Use the following steps to download and install HAXM:

13:56 Executing tasks: [:app:assembleDebug] 13:56 Emulator: Incompatible HAX module version 3,requires minimum version 4 13:56  Failed to create HAX VM No accelerator found. failed to initialize HAX: Invalid argument.

Comments
  • When I uninstalled HAXM originally, I re-installed it through the SDK manager. The current version is 6.0.3. I will check about the Intel VT-x
  • Ok. You may also need to update Repository then clean and build project
  • I followed the link here kb.parallels.com/en/5653 to determine whether my VT-x was enabled. This just tells me whether it's supported or not, but it also told me that I would need to check for firmware updates. I did so, found an update, restarted my computer, and tried to load up an emulator and it worked. Not able to confirm whether it was simply the restart that worked or if updating firmware did it. So I will mark this as the accepted solution since it lead me to the right answer.
  • I think the update had something to do with fixing the problem. That's awesome :-)
  • I am facing the same issue with my Mac, and I have everything updated, and VMX is one of the entry. but still facing the issue.
  • Certainly helped. And a reboot is definitely necessary, even on a mac.
  • Thanks, I found intelhaxm-android.exe in this folder (windows), ran it and it told me that older version is installed. Install new? Ok! And after that emulator is working ok.
  • This was the issue for me. Suspending the Parallels VM made it work again.
  • Yup, Parallels was the culprit for me too. A suspend is a LOT quicker than a reboot.
  • This was my fix as well! Suspended Parallels VM on my Mac.