News Windows 11 TPM 2.0 requirement suddenly leaves virtual machines users locked out

I'm really confused by this article. This doesn't leave virtual machine users locked out and doesn't require any form of physical TPM if you're on a server. Just enable vTPM support that comes with vCenter v7.0.2 and give your virtual machine a vTPM. Works without issues, not sure what the big deal is. vTPM is already a requirement in DOD / Government networks for Server 2019 and newer. Is the fact that this article is saying that it's going to cost money to use Windows 11 as a VM, because if so, that's not true either. If your hardware supports Windows 11 with a physical TPM, then you can also install a Windows 11 VM on that guest OS without issues. This article is really misleading and just trying to spread misinformation. You don't need a physical TPM in HyperV servers for Windows 11 either.
 
Please stop these fake news. A virtual machine has a virtual TPM. This has nothing to do with the physical machine or with the presence of a physical TPM in it. Nothing is changing for VMs.

Of course you are not going to use your physical machine’s TPM directly and/or forward it into a virtual machine (even though you can). For two reasons:

First, you do not want dangerous and untrusted game console firmware to ever touch your TPM and its key slots. B-class closed-source software waste belongs into a safe virtual machine container with a virtual TPM, not on real hardware.

Second, your virtual machine should be, ideally, live-migratable or, at the very least, offline-migratable. For that reason you need a virtual TPM that migrates with it, not a physical TPM that hardwires it onto one particular physical host.

This entire piece of hoax translates into:
— open your virtual machine settings (e.g. virt-manager),
— add a virtual TPM to the virtual machine,
— Click — Click — Done!

FFS, why is there so much fuss around it??? The interwebs are full of this nonsense. Ain’t there any real problem to write about?