Host computer running Windows 7 and VMWare Workstation

VMs under VMWare Workstation

(*) Both VMs have hypervisor.cpuid.v0 = "FALSE" in the .vmx file

(*) Both VMs have enabled "Virtualize Intel VT-x/EPT or AMD-V/RVI" under Hardware->Processors

Have one VM with Windows 8.1 with VS 2013 and VS 2015

(*) All options under Hyper-V (total of 4) are checked

(*) I have two VMs under Hyper-V Manager; two Windows Phone Emulators

(*) Hyper-V Virtual Machine Management service running

Have another VM with Windows 10 and VS 2015. Windows Phone emulator does not run.

(*) All options under the Hyper-V tree (6 total) are checked

(*) Don't see any VMs under Hyper-V Manager

(*) Hyper-V Virtual Machine Management service running

So, when I try to run an app on an emulator (Windows 10) I get the following error:

Windows Phone Emulator requires Hyper-V. Your computer is missing the following pre-requisites required to run Hyper-V

- Second Level Address Translation

0x80131500

• Moved by Jamles HezMicrosoft contingent staff Thursday, August 13, 2015 2:15 AM
• Moved by BrianEhMVP 16 hours 31 minutes ago

Hi meareal,

Move to Hyper-V forum for a better support, thanks for your understanding.

--James

You cannot run Hyper-V (which the phone emulator requires) and Hyper-V on the same machine at the same time.

VMware Workstation breaks the networking stack for Hyper-V.

And Hyper-V requires hardware access to the virtualization extensions of the chipset.

Hello Brian and thank you for the response. 

If I am able to run the phone emulators on a VM running Windows 8.1, why can't I run the phone emulators on a VM running Windows 10? Same host for both VMs.

I was hoping I had missed a configuration setting somewhere. Anything I can do to address this problem on Windows 10?

Ah.

Good question.  That said, there are lots of changes in Win10 that might be incompatible with nesting it this way and getting things to properly work.

There are many aspects of the OS that are different at the kernel level.  And enabling virtualization in a VM has never been in the testing matrix, it just seemed to work in the past.

That said, your key error is: Second Level Address Translation

Which is interesting, since Hyper-V under 8.1 has the same requirement.  But the Windows 10 VM is not seeing the SLAT (Extended Page Tables) feature of the underlying hardware.

Run CoreInfo in the OS of each VM with the -v option and that will tell you what the OS is 'seeing'.

I am guessing that the Win10 VM is not detecting SLAT, therefore not starting the Hyper-V hypervisor.  And this is now an absolute hard requirement that cannot be avoided in any way at all.