When VMware announced the new licensing model based on vRAM when they revealed vSphere 5 the ensueing uproar overshadowed all the great features and enhancements that are part of vSphere 5. In fact if you look at my vSphere 5 link collection you will see that there are more links about licensing then there are about everything non-licensing related in vSphere 5. There was also a thread started in the VMTN forums on licensing and it is currently 87 pages long.
Well VMware heard you loud & clear and is changing the licensing model in a manner that should make almost everyone happy. I was fortunate to be on a pre-briefing call with VMware on the licensing changes and one of the points I brought up to VMware was how could you not of expected this reaction. If they had consulted with customers, vExperts and some other key people they could of seen what the reaction was going to be like and not be in the position they are in today. VMware said they kept this mostly internal which was not a good idea when making changes that would have a big impact on customers. VMware had calculated that only a very small percentage of there customers would be affected by this. I asked them how did you calculate this and what percentage of your customers did you get this information from. They responded that they use information obtained from logs that are sent in when support requests are opened and vm-support bundles are typically sent in which documents a persons environment.
To VMware’s credit they listen to their customers though, many other companies would just go ahead with the changes regardless of how customers felt about them. While VMware didn’t directly respond to the 87 page forum thread they did read every single post in it to see what customers were saying about the licensing changes. So the end result is VMware addressed some of the key concerns that customers were making with licensing. Here is a summary of feedback that VMware obtained from customers & partners:
- With no cap on vRAM licensing the monster VM with 1TB of vRAM would cost $38,445 to license.
- Entitlements were too low and while it would only affect a small percentage of customers it would have a big financial impact.
- Penalized customers for short lived usage spikes that may not occur on a frequent basis.
- The 8GB cap on the free version of ESXi is too low and doesn’t make it that usable.
So VMware responded to each of these concerns to licensing in vSphere 5 as follows:
- The amount of vRAM counted per VM has been capped at 96GB. So a 1TB VM would now only use 96GB from the vRAM licensing pool and only cost $3,495 to license.
- vRAM entitlements have been changed as follows:
- To help against spikes in memory usage it now uses a calculated 12 month average of configured vRAM rather than a high water mark
- The vRAM limit for the free edition of ESXi has been raised from 8GB to 32GB.
One other question I had for VMware was whether they have to modify the vSphere 5 RC code now before it goes GA to update it with these new licensing changes. My main concern was the hard limits imposed on the Essentials and free edition of ESXi. VMware responded that they have actually not applied any hard limits to the code yet so the GA version of vSphere 5 will not enforce any hard limits at all. This will be considered a bug and will be resolved in the next update of vSphere 5.
To make it easier for customers to see how the licensing changes will affect their existing environments VMware is releasing a vSphere Licensing Advisor Tool. It is an application that can be installed on any Windows computer that connects to vCenter Server and collects information about your environment. The information gathered is a point in time picture of vRAM usage, you can exit the tool and re-run it if you want to get updated vRAM usage numbers. The tool maps editions to the vSphere 5 equivalent edition using standard entitlement paths. It does not capture information on Linked Mode and instead calculates pools as if all vCenter Servers are linked together. The tool also caps the amount of per VM vRAM usage at 96GB. The results of the tool can be exported to a CSV file so data can be more easily viewed. Here are some screen shots of the tool in action:
So there you have it VMware heard you loud & clear and did what was needed to fix the mess they created. I hope you understand VMware had to do something to change the licensing model because the socket model just doesn’t work anymore with the way core counts keep increasing. It would of been nice if they had implemented these new changes originally so the reception to the vSphere 5 announcement focused on the features and not the licensing but what is done is done, VMware fixed it and now its time to move on. I really have to give them a lot of credit for so quickly responding to customer feedback and trying to make things right with their customers. While there are some that may still not like the new licensing model, it’s definitely better than before and since it is here to stay its time to start getting used to it. So lets start getting excited about the features in vSphere 5 and not fixate on licensing anymore. This promises to be another great release from VMware that makes an already great product even better.
Great post, thank you.
Great Post Eric!
I’ve had one question that has puzzled me a bit.
Where does VMware get the 12Month average data? Will they store their own file/db or use vCenter?
I am curious since if vCenter DB is lost, rebuilt, etc. you could lose several months worth of data and not be able to accurately determine your 12 month average usage.
Sure it’s a Great Post …
Is the vSphere Licensing Advisor Tool already available for download ???
So does VMware just want to hand the entire small/mid sized market to Microsoft? Does no one remember what happened to the fileserve giant Novell when they arrogantly kept prices so high?
Is anyone actually buying that a 32gb memory limit which is the amount of memory we were buying for our vmware 2.5 servers 6 years ago is somehow not going to impact many people?
Nice article, thanks for the information.