Cannot launch an x86 Android emulator using Hyperv, but can with HAXM, why?

0

I asked this question a few weeks ago: Does my CPU/motherboard support VT-x?. I have a Core I7 950.

I am having problems running X86 Emulators on my Windows 10 PC. When I Start an emulator in Visual Studio 2017 (or 2019) I see this:

enter image description here

I have followed the instructions here. Please see the screenshot below:

enter image description here

If I uninstall Hyperv and Hyperv plaform (using Windows Features) and install Haxm then the problem goes away and everything works as expected. However, I cannot use Docker.

The answerer of my previous question suggested that Hyperv may only work with Android on ARM based processors. However, I have set all of this up on my new work laptop, which has an intel processor and is Windows 10 and everything works as expected. If I run the command DOS command above on my work PC then I see this:

enter image description here

Notice there is no EPT/UG warning. My work PC is i5-8250U.

Could this have something to do with what the command prompt is saying i.e. missing EPT + UG Features? The answerer of my previous question says my CPU supports these features. Do I need to do something in the BIOS to enable them?My research is telling me that UG is only supported on Westmere CPUs onwards. However, my CPU is Bloomfield.

Update

I have disabled Hyperv on my work PC (where I have no problems) and my home PC (where I do have problems) to run the Intel CPU Identification Utility. Here was the result of the work PC:

enter image description here

and here is the home PC:

enter image description here

I read this post here: Visual Studio 2019 Android Emulator not working. The OP has the same CPU as me and I see the same output as him when I try to run the emulator from the command line:

WHvGetCapability failed. hr=0x00000000 whpx_cap.HypervisorPresent? 0
cpu
motherboard
bios
android
asked on Super User Sep 14, 2019 by w0051977 • edited Sep 15, 2019 by JW0914

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0