Do you even know what VT-d does? Most people who do virtualization have little to no use for VT-d. The only time you need VT-d is if you plan on passing real hardware to a VM which requires a lot of work on the host OS to "detatch" the device from the host OS then re-initializing it in the VM, which even a lot of cloud setups don't do. VT-d is rarely used outside of servers and it's geared to a particular kind of virtualization workload. I suspect more of the people in the world wouldn't know the difference if they had it or not. The only situations I can think of where VT-d would be required would be to pass through a RAID controller to give a VM improved I/O (also keep in mind that the RAID and its drives would be dedicated to a single VM,) same deal with ethernet adapters if you've virtualized your gateway server, or if you're trying to do GPU passthru in a VM. All are legitimate reasons for using it but, most people won't be doing any of those things. Just an FYI. K-edition CPUs have the extension that really matters for VMs, which is VT-x.
There are low power Skylake chips that keep up with my 3820 just fine.
I suspect they have that backwards or I'm up too late and imagining things.
