Nested Virtualization is not a new idea. In fact, we announced our first preview of Nested Virtualization running on Windows way back in 2015. From that Windows Insider preview to now, Nested...
Updated Jun 13, 2020
Version 2.0
Blog Post
I think currently, where Win11 is so near the best idea is to just jump into Preview builds on host when nested virtualization is a must for you. I would just not do much stuff on a host system and leave it only with device drivers installed and HYPER-V enabled - having so small amount of features used/configured should not poses a big risk your host system will crash after next preview build installed. This should be far less costly way than just doing a new build with an inferior Intel CPU.
Because Windows 11 builds are far greater than 19636 the nested virtualization on AMD will for sure be part of final release in my opinion. If you will invoke Get-VMHostSupportedVersion command on Win11 preview build you will see it supports by default version 10 of HYPER-V which is the same of the one used in Windows Server 2022. That version of HYPER-V fully supports nesting on AMD hardware. I have that Win11 preview build on my machine (Ryzen 3700x) and nesting is working just fine on it (I am even able to launch such old systems like Windows XP x64 as a level 2 guest without any issues - of course newer systems also work without issues for me like Windows 10 + Hyper-V + Docker in level 1 guest).