HAXM and Lollipop

与世无争的帅哥 提交于 2019-11-28 06:13:48

I had the same issue when creating a Nexus 6 AVD with an x86_64 image and it appears the HAXM does not support that on an old Core 2 Duo (Mac Book Pro late 2009 for example).
This is specified in the Release note known issues in $ANDROID_SDK_HOME/extras/intel/Hardware_Accelerated_Execution_Manager.

HAXM driver does not support emulating a 64 bit system image on Intel systems based on Core microarchitecture (Core, Core2 Duo etc.). All systems based on Nehalem and beyond are supported. (Corei3, Core i5 and Core i7 machines).

Try the newest HAXM provide in Intel official site https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager-end-user-license-agreement-macosx ,now is 1.1.1.The one which from sdk manager is still old 1.1.0. it works for me.

It seems that the SDK manager automatically installs HAXM 1.0.8 instead of 1.1.0/1.1.1. To fix this, navigate to

<android-sdk>/extras/intel/Hardware_Accelerated_Execution_Manager

and reinstall HAXM by executing

$ chmod +x silent_install.sh
$ sudo ./silent_install.sh -u
$ sudo ./silent_install.sh

The emulator should boot properly now.

Upgrading to the latest HAXM may not be enough (current version to date is 6.0.1).

You can still begin with a HAXM update, but if you run an older CPU such as a Core 2 Duo, you should definitely choose an x86 version of your virtual image, not x86_64.

When I started my first wear emulator it was fine until today when after restarting my MacBook Pro I've experienced the crash VCPU shutdown request. The version of HAXM I'm using is 1.1.4. So I tried restarting, recreating emulator images... Nothing worked until I've reinstalled the HAXM driver using .dmg installer in /extras/HAXM... folder. Just FYI

Jaeseok Jay An

I recently upgraded to El-capitan os, and I've encountered same problem.

First, uninstall HAXM throughly.

sudo /Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh 
sudo rm /System/Library/LaunchDaemons/com.intel.haxm.plist

Second, reinstall HAXM with latest version. https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager

This solved problem for me.

Following is the link i referred to HAXM on OS X keeps on disappearing

Solved! Apparently, I was using HAXM 1.0.8 which is the latest version that is available at Intel's site. However, Android SDK Manager downloads a preview version on HAXM 1.1.0 which is required to run 64bit images.

If you are using Android Studio 0.8.13 or older, then upgrade it to latest. This issue is fixed in 0.8.14 Release.

It works with the latest Android studio after upgrading the SDK component to:

Intel x86 Emulator Accelerator (HAXM installer), revision 5.2

Solved the issue. You need to do these things:

  • Uninstall old HAXM: sudo /System/Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh
  • Disable kext signing: apparently HAXM 1.1.0 is not signed appropriately sudo nvram boot-args="kext-dev-mode=1". Reboot
  • Install the new HAXM 1.1.0 as usual (notice that if you don't disable kext signing, haxm will refuse to install with the error that VT/NX is disabled)
  • Add $ANDROID_HOME/tools/lib to your $LD_LIBRARY_PATH

API 21 AVD images work without a hitch for me now.

Source: http://www.csell.net/2014/09/03/VTNX_Not_Enabled/

Try to reduce Memory Limit used by HAXM.

https://software.intel.com/sites/default/files/managed/86/82/ss-mac-3.png

This works for me.

1- Update HAXM Accelerator to revision 5.2 From your SDK Manager

2- Install the new Updated HAXM (no need to uninstall the previous) -> (Restart the System)

3- Make the AVD of Lollipop Using following Configuration.

hope this helps

Now there is a new version HAXM 1.1.1 and it has a different version for Mac OS <10.9 and >10.9.

Updating HAXM from download manager worked for me. It's not downloaded automatically when you upgrade your system to android 5.x

if after the update it still doesn't works get a wipe data on your emulator and don't load it from snapshot because the problem is here, it's corrupted it just happend to me right now and iv got it solved this way

I had a similar issue when I booted a Vagrant VM simultaneously. It then sent a VCPU shutdown request. Also the Android emulator wouldn't boot when a Vagrant VM was running. I hope this could help anyone.

emulator: VCPU shutdown request

EAX=00000000 EBX=c085e000 ECX=01000000 EDX=00000000
ESI=00000000 EDI=c0860000 EBP=c085ffbc ESP=c085ffb4
EIP=c02065cf EFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =007b 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
CS =0060 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
SS =0018 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
DS =007b 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
FS =0018 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
GS =0018 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
LDT=0000 00000000 00000000 00008200 DPL=0 LDT
TR =0020 00001000 00000067 00008900 DPL=0 TSS32-avl
GDT=     0086a2c0 0000001f
IDT=     00000000 00000000
CR0=8005003b CR2=b6ec0004 CR3=3666b000 CR4=00000690
DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000 
DR6=ffff0ff0 DR7=00000400
emulator: Failed to sync vcpu reg
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!