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 never said nested Hyper-V was not as important for AMD as it is for Intel users. I said it's not that common of a need, for both.
Now here is where you clearly show how dishonnest you are : Ryzen 3600 was released in July 2019. MS had not acknowledged nested Hyper-V would be a thing by that time. (source : date of the first acknowledgement by a member of the dev team on Uservoice) Stop trying to retcon things. This means either two things :
- you bought an AMD CPU knowing you needed nested Hyper-V and it was not supported, in which case this makes you a clown.
- you bought an AMD CPU not knowing by that time you would need nested Hyper-V in the future, in which case that makes you unlucky. Guess what? That happens. All the time.
Your bang for buck approach is super cute, but usecase still is the first criteria. Now again, if you didn't know by that time, shit happens. So yes, my advice is : if it can wait a few more months, you're all good. If you can't, there are i5 10400 and B460 mobos for cheap all over the place. And if you CAN'T (and I say can't, not "don't want") wait that means you are making professional use of it at a modest level (if that were not the case, we wouldn't be discussing 3600 and 10400) and yes, the few bucks are worth the investment. No matter what nice fairy tail you want to believe in, investment is still a thing. Does it suck sometimes? Yes. Is it a reason to start going mad at MS or whoever? Seriously not. If you think so, you really need a theraprist dude.