For those following this thread, I wanted to post some info that may be helpful.
I have been doing some testing and it appears that we can get Hyper-V to work on the MBP on all of our units except the 2016 MBP with Touch Bar, I also tested using latest Fusion 8.5 and Parallels 12 at time of this post with Nested Virtualization enabled on both products. Here are scenarios/results I have tested:
17" MBP - Team loved large screens. Was sad to see them go.
Even though officially unsupported, we pieced Boot Camp drivers together to get full Windows 10 support
Requires warm boot from Mac to Windows to set the HW virtualization flags
Hyper-V runs in Boot Camp
4GB Memory Limitation makes them pretty unusable for serious Dev or virtualization
2014 15" MBP 16GB and latest 2015 15" MBP (2015 Models purchased 2 months ago from Apple Store)
Requires Warm Boot to set the HW virtualization flags
Hyper-V will then run in Boot Camp natively
Parallels has odd issue with Nested Hyper-V (Nested W10 was confusing keyboard input refusing sign-in). (Parallels announced they have issue with multi-proc nested virtualization VM settings that they are working on.)
Fusion runs nested Hyper-V
2016 15" MBP 16GB (Models purchased from Apple Direct through Apple Store)
WIndows 10 hangs after Hyper-V turned on regardless of Warm Boot Flag Set or Not
Did not try Parallels due to issue described above
Fusion allowed me to enable Hyper-V without reboot hang
Fusion then runs Nested Hyper-V
Then tried booting into Boot Camp hoping Hyper-V would behave after getting through install inside Fusion. It locked the machine again.
Seems to be just the latest model. I have escalated case with Apple and Microsoft. No word yet from either. May not get very far due to holidays. We have until 1/8/2017 to return either 2015 or 2016 units, which at this time is very probable that we will return 2016 units.
