Posts

Showing posts with the label multi-core

VMware Multi-Core Pricing & Licensing Policy

I am been called up today on my off day but am not complaining.  It got be to refer to my own post awhile back here in August after VMworld 2012 on the licensing on vSphere 4.x. VMware actually updated the EULA on multi-core licensing and pricing which you can refer here .  This has been quite while back. There is no reason why anyone would still insist to setup a new vSphere environment based on vSphere 4.x with all the limitation and functions set. I think the new EULA multi-core policy would explain for those who are still using vSphere 4 and have a new hardware which exceed your vSphere 4.x edition license entitlement which is pretty common having that most of them are 8 cores and above now. The policy give you a very good example.  I share just explain this with one scenario I was asked today. I have purchased 4 x vSphere 5.x Enterprise Licenses for a server with 4 CPU of 8 cores each.  I downgrade them to vSphere 4.x Enterprise.  So vSphere 4.x...

vSphere 5 & 5.1 Licensing

As of today's announcement, the new vSphere licensing for 5 and 5.1 will be by per processor licensing moving forward from 27th August 2012.  This eliminate the need of vRAM entitlement which was used in vSphere 5.0 last year. This come effect for all new and existing customers on vSphere 5.0 while vSphere 5.1 is yet to be released for download.  The updated End User License Agreements (EULA) will replaces and supersede statement can be found here . This change was decided due to the feedback and confusion created when vRAM entitlement was release last year in partners and users.  Though vRAM would benefit people with bigger environment, the core processor licensing was still easier for everyone. You can read from the vSphere 5 Licensing white paper here .  You may also refer to all the resources of vSphere whether for 5.0 or 5.1 all at this place . I have the table of the license entitlement between 4.1 and prior and the new change for 5.x below: ...