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 12, 2020
Version 2.0
Blog Post
All of you defending Microsoft are talking total BS.
Facts:
1 - AMD SVM (virtualization extensions) are pretty much the same Inc the previous gen before Ryzen CPUs. So Microsoft has more than 4 years, more like 10 years o give sm feature parity with Intel on HV.
2 - Linux KVM supports SVM and has done for many years.
3 VMware support SVM and has done for many years
4 virtual box supports SVM and has done for many years.
5 Microsoft blocks other hypervisors from running when Microsoft HV is enabled.
6 hyperv has willingly not supported SVM for over a decade when they are supposed to be neutral and hardware agnostic
7 amd SVM works on Linux and windows for any company that wants to support those extensions. They are CPU features and extensions. You don't need permission from AMD to send supported instructions to your CPU.
8 Microsoft has forced hyperv use upon everyone by pushing wsl2 to make windows a more useful Dev machine.
9 no one cares about hyperv not supporting SVM before because and CPUs where not popular and you don't have to use hyperv because it was so rubbish.
10 now you have to use hyperv for wsl2 and docker. So you lose other virtualization engines like VMware and virtual box. But also now you lose nested SVM too.
Microsoft this is very very wrong very very unfair and very illegal and very drastic monopoly criminal like behaviour. How can you willingly cripple consumers hardware because they bought the CPU brand that does not pay you a commission? Your company should be broken up into small pieces like azure. Web is software hardware ect. Maybe then you will stop doing these crimes against customers.
It is very very wrong how you have treated and fans and you should pay us all massive amount of compensation.