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
Instead of getting personal let's stick to the facts.
1) AMD has had virtualization enabled CPU's for years.
2) AMD is (at least now) definitively better choice over Intel - performance or $ wise.
3) Microsoft has not implemented it in their own virtualization tech - Hyper V that they are pushing for quite strongly, driving out competition.
4) If we do not complain - nothing will change for sure.
5) Since we complain to Microsoft and Microsoft stays silent - that means we are in the right place - if it was AMD's fault, they would happily point the finger at AMD.
6) Pain index to get this backported is too low - therefore we have to increase pressure on MS to do it, otherwise it will stay in low prio.
or just switch to Linux KVM with GPU passthrough and install windows there for all the essential apps you cannot run from your distro. Which looks every day better as MS stays silent over this important, essential and otherwise basic feature.
Personally, I do not believe MS could not have implemented it earlier. Hard to believe also that AMD bumped core counts up to 16 in consumer space without having Virtualization in mind completely. if there was solid evidence AMD virtualization tech was bad we would have heard about it already. Besides - it does work on Linux, yet does not on Windows - so what gives?