Licensing changes brought by vSphere 5.1 release - no vRam entitlements

While I have been torn apart by temptation to learn all new features of vSphere 5.1 by creating a long list of documents and blogs to read I have missed probably the most important change in VMware vSphere Licensing model - the is no more vRAM entitlement/limitation.

VMware claims they have carefully listened to their clients:

"Our customers spoke clearly," VMware Chief Marketing Officer Rick Jackson said at a press conference after Monday's opening keynote. "They don't want to think about things like vRAM. We're changing it back to what our customers want."

To me it seems more like another answer to Microsoft Hyper-V 3.0 which is about to be released and has already changed the virtualization market's landscape. But I personally liked the fact that VMware has enough courage to admit they had made a mistake with presenting vRAM.

"Yes, it is an admission that we had made things overly complex, and we are rectifying that mistake," outgoing VMware CEO Paul Maritz says bluntly. "Mea culpa."

So, there is no more vRAM and Cores per CPU limits now. Plain and clear licensing model with only requirement to have 1 license per each CPU/Socket in your server. It is quite an improvement which definitely makes life of VMware customers and VMware salesmen easier. I guess the total number man-hours spent last year worldwide in debates about vRAM could have been sufficient to build a space ship.

Another significant benefit of new licensing and pricing model is that all vSphere editions (except Essentials Kit) have gotten plenty of nice features included:  vSphere Replication, vShield Endpoint, High Availability and Data Protection (previously known as VMware Data Recovery). 

Free vSphere Hypervisor's limitations have caused some confusion as different part of VMware website and documents were providing different information. Here is the latest and most precise information from GabesVirtualWorld

“There is no vRAM in vSphere 5/5.1, including the free vSphere Hypervisor. If a host licensed with vSphere Hypervisor has more than 32GB of physical RAM it will error when applying the license or on boot. Before the vSphere Hypervisor license is applied, it will be running in 60-day evaluation mode (functionally equivalent to Ent+).  So in the case of a host with more than 32GB of physical RAM, when assigning the vSphere Hypervisor license fails the host will remain in the evaluation mode. If they do want to proceed they either need to find a box with 32 or less or go into the BIOS of the offending machine and turn off the additional RAM.”

The last interesting new fact is the special vSphere Standard edition which includes vCenter Operations Management Suite Advanced and vCenter Protect Standard. I am wondering why there is no similar Enterprise Edition? 

Now I am looking forward to the 11th of September when vSphere 5.1 will be available for download so I can start rebuilding my home lab.


If you find this post useful please share it with any of the buttons below.

Multiple complaints forced VMware to change vRAM Entitlements

As far as I am aware right after VMware had started to receive tons of negative feedbacks regarding new licensing model of vSphere 5 they began reviewing the clients' current vRAM usage. I guess they questioned quite a lot of clients to compare the current amount of physical RAM and actual vRAM assigned and made a proper conclusions.

So here are the latest rumors and I personally truly believe they will come true. 

• vRAM entitlement per Enterprise and Enterprise Plus license is going to be doubled to 64GB and 96GB corresspondingly. 
• vRAM entitlement per Essentials and Essentials Plus license will be increased from 24GB to 32GB.
• Maxumum vRAM for Essentials /Essentials Plus will increased to 192GB
• Maximum 96GB per VM will be counted against your vRAM pool limit even though you might assign 1TB to this VM.

Honestly, I think it is very adequate response to all criticism VMware got for the last few weeks, but I am wondering - why VMware marketing guys couldn't foresee such reaction? Perhaps it shows that VMware was not fully aware about how their products were used in client companies. I guess now VMware will arrange such kind of resource usage reviews on a regular basis.  

Taken from here: http://derek858.blogspot.com/2011/07/impending-vmware-vsphere-50-license.html

Update: Official announcement of vRAM entitlement change is expected on 3rd of August.

Update 1: Official announcement is here - http://blogs.vmware.com/rethinkit/2011/08/changes-to-the-vram-licensing-model-introduced-on-july-12-2011.html

Here is comparison table to the changes that were announced on 12th of July.

Another nice thing to mention - vRAM usage will be calculated as an average amount used for last 12 month. So rare spiky raises in usage of vRAM will slightly increase average vRAM usage, but you will not need to pay for such spikes perpetually.   

If you find this post useful please share it with any of the buttons below.