Tag: RVtools

VMware Licensing Change – Per CPU and Per Core
VMware is pushing out a change on how it licenses ESXi.
We are all familiar with the per CPU Socket model that has been in existence for some time (since the release of ESXi 1.x).
Well, now they are moving to per CPU with a max of 32-cores.
While that may not impact you right now, as CPU core counts go up, this will be something you have to deal with…maybe the next year or two.
What happens when you get a 36-core CPU? you will need 2 x CPU licenses to run ESXi on that.
Why don’t they just change their licensing to strictly be per core?
I don’t know…they didn’t ask me.
I truly believe if they want to start addressing cores, then just go straight core, and forget the CPU socket count. They already have figured out how much per core licensing would cost (~$118 or so, given the cost of ESXi Enterprise Plus per CPU socket licensing). Why not just do per core then?
With a mix of CPU socket and Core Count, I can see the nightmare coming….just like the vRAM Tax fiasco of the vSphere 5.0 release.
Remember that?
Having to do different designs for each solution to figure out the most cost effective way to deliver a mix of CPU and memory and determining how many hosts in each too.
I have no problem changing the licensing from CPU Socket to core, if that’s what you want to do.
I do have a problem with keep CPU Socket licensing, and limiting the number of cores to 32 per socket. Adding unnecessary design constraints to something in this manner will be a pain….again, not today, but next year & forward. If you run the new AMD chips (with 64-cores), you now have twice the expense to run ESXi on it…..
This happens on April 2, 2020.
Read the VMware News Post here.

Intel – another CPU vulnerability
Got another one to be aware of now.
Bob Plankers put out a post about these new vulnerabilities.
Nothing for us to do yet, as Intel hasn’t shipped a code-fix, but as long as you are patching your vSphere environment, you should be covered.