PD11 Nested Virtualization Hyper-V No Longer Working

T

TS-Micah

Product Expert
After updating to 11.1.2 and then downgrading after the BSOD loop fiasco, I haven't been able to get any Hyper-V virtual machine or WP emulator to run at all.

System:
MacBook Pro (Retina, 15-inch, Mid 2014)
Processor: 2.5 GHz Intel Core i7
Memory: 16 GB 1600 MHz DDR3
GPU: NVIDIA GeForce GT 750M 2048 MB

Parallels Desktop Pro 11.1.1 (32312)

Here's output from CoreInfo.exe -v:
Code: 
Coreinfo v3.31 - Dump information on system CPU and memory topology
Copyright (C) 2008-2014 Mark Russinovich
Sysinternals - www.sysinternals.com

Note: Coreinfo must be executed on a system without a hypervisor running for
accurate results.

Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Intel64 Family 6 Model 70 Stepping 1, GenuineIntel
Microcode signature: 0000000F
HYPERVISOR      *       Hypervisor is present
VMX             -       Supports Intel hardware-assisted virtualization
EPT             -       Supports Intel extended page tables (SLAT)


I do have the Nested Virtualization option checked...

Does anyone else have this issue?
 
Here's the Problem Report ID: 87541430

Could this possibly be related to the BSOD loop I encountered when I updated to 11.1.2?
 
Now this is interesting, when I boot the Windows 10 VM using a Clonezilla DVD ISO and switch to another terminal and run cat /proc/cpuinfo - this shows up (notice VMX and EPT are in the list, interesting... ):
Code: 
processor     : 0
vendor_id     : GenuineIntel
cpu family     : 6
model       : 70
model name     : Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
stepping     : 1
microcode     : 0xf
cpu MHz       : 2494.284
cache size     : 6144 KB
physical id     : 0
siblings     : 4
core id       : 0
cpu cores     : 4
apicid       : 0
initial apicid   : 0
fpu         : yes
fpu_exception   : yes
cpuid level     : 13
wp         : yes
flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx rdtscp lm constant_tsc nopl xtopology nonstop_tsc eagerfpu pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm arat pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 invpcid xsaveopt
bugs       :
bogomips     : 4988.56
clflush size   : 64
cache_alignment   : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

This is the output from sysctl -a | grep machdep.cpu.features from KB5653
Code: 
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
 
Last edited:
Update:

I discovered that CoreInfo reports differently once Hyper-V is uninstalled....
Code: 
Coreinfo v3.31 - Dump information on system CPU and memory topology
Copyright (C) 2008-2014 Mark Russinovich
Sysinternals - www.sysinternals.com

Note: Coreinfo must be executed on a system without a hypervisor running for
accurate results.

Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Intel64 Family 6 Model 70 Stepping 1, GenuineIntel
Microcode signature: 0000000F
HYPERVISOR      -       Hypervisor is present
VMX             *       Supports Intel hardware-assisted virtualization
EPT             *       Supports Intel extended page tables (SLAT)

So after discovering this, I uninstalled/re-installed Hyper-V several times and had no luck.

During the process I discovered several Hyper-V switch drivers installed in the device manager and removed them.

For some odd reason, and I'm not sure how this happened, but running the net localgroup administrators /DELETE commands listed at here seemed to have resolved the issue.

Here they are for convenience:
Code: 
net localgroup administrators LOCAL /delete
net localgroup administrators SERVICE /delete

In addition the Windows VM was at one time a member of a Windows AD Domain, but is no longer. Perhaps this could have contributed to the problem as well?

Given this issue has been resolved, I wonder what would happen if I upgrade to 11.1.2 again if I would get the BSOD loop...
 
TS-Micah said:
Here's the Problem Report ID: 87541430

Could this possibly be related to the BSOD loop I encountered when I updated to 11.1.2?
Click to expand...
Hi, please be informed that Parallels Desktop 11 Update 1 Hotfix 3 (11.1.3-32521) was released and the issue has been addressed. You can update to the latest build as suggested in this article. Latest version always available here: http://www.parallels.com/directdownload/pd11/ Please note that Parallels Tools also needs to be updated (Actions > Update Parallels Tools) and let us know how it works. Thanks! PC
 
You must log in or register to reply here.
Back
Top