emulator: failed to create hax vm on mac

Emulator: Failed To Create Hax Vm On Upgrade From 4
Emulator: Failed To Create Hax Vm On Android Emulator Launches

It appears to be non-exclusive all the way back to its first appearance in r14905.

I can launch my virtual machines with no problem using any version of VirtualBox.

However, when I run versions 4.3.29-revision101478 and 5.0.0-revision101495 I cannot launch Intels HAXM emulator (as part of Android Studio Android Development) because HAXs error message says.

However, when I run version 4.3.28-revision100309 I can launch both at the same time with no problems.

Im on a Mac.

Emulator: Failed To Create Hax Vm On Upgrade From 4

I have the same issue immediately after upgrade from 4.3.28 to 4.3.30.

Theres no issue with VirtualBox machines - they run fine, but Android emulator gives aforementioned errors emulator: Failed to sync vcpu reg emulator: Failed to sync HAX vcpu context and does not start or stops or crashes, so you cant use Android Studio.

I rolled back to 4.3.28 and that immediately fixed the issue - Android Emulator that comes with Android Studio works again in parallel with Virtual Box machines.

I first started the Virtualbox application, then launched the Android Emulator from Android Studio, then launched Windows 7 from Virtualbox.

Then I exited the Android Emulator and tried relaunching Android Emulator while the instance of Windows 7 is still running from Virtualbox.

I just tried 5.0.2-102096 as well and I get the same problem.

Emulator: Failed To Create Hax Vm On Android Emulator Launches

When I stop the virtualbox vm, the android emulator launches fine.

See the same issue as well on Virtualbox 5.0.8 r103449 and Android Emulator on Mac.

We need to hit a web server running in VBox from the emulator and cant.

I just updated to 5.0.10 r104061 and it fixed the issue on OSX 10.11.1 and HAXM 1.1.5.

I guess running the backend with Vagrant VBox combo caused conflicts with Intel HAXM.

I use Virtualbox both directly to host virtual OSs and for Docker, so having it demand exclusivity for the hypervisor EVEN WHEN NO VMs are RUNNING is a nasty bit of anti-social behavior.

AFAICS the Intel HAXM aborts as soon as a VirtualBox VM is started.

As long as no VirtualBox VM is running the HAXM device emulator process is not disturbed.

In order for VirtualBox and the Android Emulator to co-exist, VirtualBox must change back to shared use.

Any proof for this claim Please note that the observation that HAXM works together with VirtualBox 4.3.28 and does not work together with VirtualBox 4.3.30 is not a proof Due to a bug VirtualBox 4.3.28 did not use hostvmxon() hostvmxoff() functions which is mandatory for recent versions of Mac OS X.

Fixing this bug is most likely the reason why HAXM doesnt work together with VirtualBox anymore.

Unfortunately the source code of HAXM is not freely available (in contrast to the source code of VirtualBox) so its hard to debug this problem.

Ive searched the VirtualBox svn for references to hostvmxon and only found a hit in one file.

I even searched history of this call to see if it was ever exclusive.

Emulator: Failed To Create Hax Vm On Mac