VMware Back-Pedals On vRAM Scheme, Back To Per-Socket Pricing 70
Last year VMware introduced a complex pricing scheme based on the size of the memory associated with each virtual machine instance. New CEO Pat Gelsinger announced this week that this system (which he described as "a four letter word") has been deprecated, and VMware is back to more straightforwardly charging per physical processor. Adds reader hypnosec: "Pricing hasn't been announced yet but a file [PDF] present on VMware's site does give an indication about the new pricing."
Update: 08/28 17:18 GMT by S : Updated the headline and summary to reflect that the price is per processor, not per core.
Update: 08/28 17:18 GMT by S : Updated the headline and summary to reflect that the price is per processor, not per core.
Too late, EMC (Score:4, Interesting)
Too late, EMC, we have already discovered KVM and are happily running on it.
Re:Isn't that per socket, not per core? (Score:5, Interesting)
Not really. Sometimes there just isnt a budget for multiple machines, and it is better to start by consolidating old Windows 2000 systems off of incredibly old hardware onto newer hardware.
If the budget ever arises, we can quickly set up a full vSphere environment and migrate guests around; but there is a place for virutalization even if you cannot afford a SAN or any of the HA/DRS stuff. By consolidating, we have removed a lot of bad hardware and massively lowered switching and UPS requirements, which is incredibly helpful in this instance. The vSphere client also fits the needs of the customer particularly well, since before he relied on zillions of KVMs.
I cant go into many particulars, but sometimes youre given a bad network and not a huge budget to work with. Ideally we would have a SAN and at least 3 boxes with Enterprise licensing. We dont have that, but its not the end of the world and I still have a job to do.