VMware has evaluation license for ESXi servers. After 60 days, it expires and you have to apply a paid or free license to continue. Technically, there is a trick to reset the evaluation key by deleting two files (/etc/vmware/vmware.lic and /etc/vmware/license.cfg) and rebooting the server. It’s of course not complying with VMwrae license terms. Under some circumstances like training lab, it may be OK. Make sure to consult VMware on this if you are not working for VMware. But wait – if you are working for VMware, do you need evaluation license? In his reply to my tweet, Duncan mentioned he never saw license expiration.
The vRAM was the license model VMware used in vSphere 5.0. It basically limits the usage of virtual memory, which is different from physical memory, per license. When first announced last year, it created a lot of angry customers overnight even though VMware estimated that the license scheme wouldn’t affect most of the existing customers. Later on, VMware doubled the amount of virtual memory and implemented a cap per license, and insisted to roll out the modified license model despite strong objections from customers.
Disclaimer: These are my personal thoughts, and strictly mine.
I missed the big launch of vSphere 5 on July 12 because I was having my vacation. When I came back, I found so many discussions around the vSphere 5 licensing change. It’s understandable that people don’t like changes, especially if the changes may have financial impacts.
Technically, the vRAM pooling simplifies the licensing model, as pointed out by Carter Shanklin. Money wise,
You may be wondering why anyone would do this. This is in fact not a typical use case. You probably know that vSphere Client does not treat license keys like passwords which are not visually displayed as dots or asterisks. As a result, anyone who can access a vSphere Client can write down license keys and use them elsewhere.
Normally this is not an issue at all. What about
In my previous blog, I introduced the new licensing APIs since vSphere 4. As promised, I will write samples showing how to use the APIs.
Here is the first sample (stay tuned to next one, coming soon). What it does is to check the licenses in vCenter server for their expiration dates, and print them out in the console. You can of course save them into other format, say an CSV file so that you can use Excel to further analyze it. To run the sample, you must change the IP address to the vCenter server, the username/password, as would with most VI Java API samples.
Note that a license could be an
There has been a total change in vSphere licensing model since version 4. Before that, you need a special/dedicated licensing server which may be more flexible/powerful but also cause many troubles in production environment which made licensing related issues one of the top categories in tech support.
vSphere 4 has dramatically simplified the whole licensing model, and removed the licensing server. To find out how the new licensing model works, check out the VMware vSphere 4 Licensing Guide. It covers both the vSphere side and the portal with which you can easily manage your license keys: splitting/combining, etc. This article does not cover the portal part but related APIs only.
Management APIs reflect product features. If you check the latest API reference, you will find out