Forum Discussion
b25110 Enabling nested virtualization will only be visible in PowerShell and WAC but not accepted
- May 20, 2022
Hi Karl! Thanks for trying Azure Stack HCI!
The short answer is what you're seeing is actually expected. The reason is that officially, Azure Stack HCI is only supported on physical hardware. And in some nuances, it's not the same as nested virtualization. More specifically, because Virtual Secure Mode (VSM) is enabled by default, that "hides" necessary virtualization extensions from the Hyper-V compatibility checker. That said, if you use Enable-WindowsOptionalFeature, it will bypass the compatibility checker and should successfully enable Hyper-V. So, try this:
Enable-WindowsOptionalFeature -Online -FeatureName 'Microsoft-Hyper-V'
Here's a slightly longer explanation for those curious: https://twitter.com/pronichkin/status/1294308601276719104
Happy new year Artem Pronichkin MSBernstein the procedere this still the same in WAC 2311.
I raised this feedback to the WAC team or who else the Cluster (creation) extension.
https://feedback.azure.com/d365community/idea/a9268101-e0ac-ee11-92bc-000d3ae54955