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
Artem Pronichkin MSBernstein can confirm this is the issue. WAC cluster creation does not use Enable-WindowsOptionalFeature, doing so manually solves this blocker.
Mr. Bernstein, I believe it is not worth the time, considering the guidance from Artem, to test with previous versions, as the behaviour is not OS based but rather part of the cluster creation WAC module.
I will add this to the MS ToDo list shared with the WAC team and see if they want to change this. Otherwise I could imagine that Trung is not responsible for the module, eventually EldenChristensen ?
- MSBernsteinMay 27, 2022MicrosoftPassing the suggestion to the WAC team makes sense. I imagine there is some tension between wanting Windows Admin Center to support all possible scenarios, but also wanting to keep Windows Admin Center in sync with the protective checks that Artem described.
"But most importantly, Install-WindowsFeature cmdlet (just like Server Manager itself) tries to prevent you from shooting yourself in the foot, by running prerequisite checks and post-installation tasks, where applicable."- Karl-WEMay 28, 2022MVPAbsolutely.