To my knowledge, an x86 Android emulation using Intel's Hardware Accelerated Execution Manager and Windows 8 Hyperv cannot be run concurrently at the time of this writing.
The best answer would allow them to run concurrently (probably not currently possible).
The most common workaround is to uninstall the Hyperv feature completely. If you actually need to use Hyperv this is painful. A better work around can be found here. http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/04/14/creating-a-no-hypervisor-boot-entry.aspx . This forces you to reboot, but at least you're not having to constantly uninstall/reinstall Hyperv.
I'm looking for a solution which doesn't require anything to be uninstalled and doesn't require a reboot.
Save this question. Show activity on this post. Windows phone emulator requires Hyper-V to run, but Android emulator in turn requires Intel Hardware Acceleration Manager (HAXM), which is intolerant to Hyper-V.
After Hyper-V is enabled, you'll be able to run your accelerated Android emulator.
You can use an emulator with the ARM image instead of HAXM provided that you installed it in the SDK manager. Check your SDK manager to see if you have an ARM image instead for the API level you want, then go to the AVD manager and make a virtual device using ARM as the cpu. thank your for answer.
Install HAXM and Switch to x86 By using x86 bit system image, your emulator can start running at a fast speed. To implement this, just your IDE and SDK must be updated. After that whenever you select a new Android virtual device, then select an x86 bit system image there.
I don't know if this is good answer for you. I had similar problems with x86 emulator. I've switched to Genymotion - Google Play Services are working fine, and it's really fast + official plugins for Eclipse.
But you need to install VirtualBox (but it's free) so this shouldn't be a problem.
Genymotion site: http://www.genymotion.com/
This looks like it will be the answer.
http://blogs.msdn.com/b/visualstudioalm/archive/2014/11/12/introducing-visual-studio-s-emulator-for-android.aspx
I won't mark it as answered until I actually try out the RTM bits (it's in preview now), but it's a Hypver-V based android emulator. The first 2 pain points the blog post claims to solve with the new emulator are Slowness of other emulators and Conflict with Hyper-V on Windows.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With