VMware ESX & Virtual Infrastructure v3.5 -- Be Aware of Changes to Feature Levels
Looks like VMware is making some changes to the types of features at their three different price levels. Traditionally, Starter Edition gave you ESX only, while Standard added in SAN storage capability. You didn't get VMotion, HA, and DRS until you moved to the expensive enterprise edition.
With v3.5, some very critical changes are afoot...
Here's what you get with the new price levels. First of all, Starter Edition goes away, replaced by "Foundation". "Standard" and "Enterprise" remain, but with changes to what's offered. Also chaging is the "per core" "per socket" to "per processor" on the pricing. We knew this was coming as the number of processors per core got larger.
VI3 v3.5 Foundation - retailing for $995 (per two processors)
ESX Server or ESX Server 3i
VirtualCenter Agent
VSMP (the ability to add multiple processors to virtual machines)
UpdateManager (automatic updates for VMware hosts)
VCB (VMware Consolidated Backup)
VI3 v3.5 Standard - retailing for $2,995 (per two processors)
Adds HA (High Availability, or the automatic reloation of VM's to another host when a host dies)
VI3 v3.5 Enterprise - retailing for $5,750 (per two processors)
Adds VMotion
Adds Storage VMotion (live migrations of virtual disks)
DRS (Dynamic Resource Scheduler, or the load balancing of VM's across hosts)
DPM (Distributed Power Management, or the powering off of servers when load decreases)
I must stress again, that these new prices are per processor and not per core socket. This will mean a major upgrade purchase for some people. Plan accordingly.
Note also that for new enviornments, this does not include the VirtualCenter Management Server, which is an added cost of around $5000 retail.
UPDATE (11/14/07, 10:54a, gs): Fixed the "per core" to read "per socket", which is correct. Sorry for the error.

Email This!
Digg it!
Del.icio.us
Reddit!
Newsvine
Comments
Can you please clarify your "processor" and "core" definitions as they seem to run counter to everyone else. From what I see in the industry a "processor" is a physical piece of hardware that you plug in to a socket on the motherboard. A "processor" might be made up of a number of "cores".
VMWare VI3 licensing has always been per socket (or what I would class as per processor). So a system with 2 x quad core processors would require a 2 processor license not eight.
Posted by: Mark | November 13, 2007 6:03 PM
I've always used the terms "processor" and "core" interchangably. The term I think you're looking for is "socket". Multiple cores or processors can fit in one socket. VMware used to license by the socket, but they're changing that in 3.5 to by the processor/core. This is where my comment about many people getting "screwed" comes in, because they've paid for by-the-socket licensing, and now will have to 2x or 4x their investment just to maintain. Not good.
Posted by: Greg Shields | November 14, 2007 11:54 AM
I think this does tend to get confusing. Processor and core should really not be used interchangeably since, although they show up as processors they share a socket (kind of like hyperthreading was logical but still showed up as a processor to the OS). I've asked our VMware sales rep to verify this information as this will have a big impact on us. We have moved from 4 socket/8 core blades to 2 socket/4 core blades just to keep the ESX licenses down in cost. Do you have links to where you got this information from? VMware's site is not forthcoming as I poke around.
Thanks.
Posted by: Mark Dean | November 28, 2007 9:44 PM
I received a response from my VMware sales rep. Here's how it breaks down currently: You can have up to 4 cores in a socket before you have to pay more than what we have been used to. So a quad core 2 socket server will still only need a 2-CPU or socket license.
So that means as Intel/AMD moves to 8/16/32 cores we have to budget for more money for licenses. Of course by the time these higher core counts become ubiquitous virtualization will have become so common and competition so fierce that the licenses will probably be much lower than even now. We'll see-good times for those of who make a living providing virtualization solutions!
Posted by: Mark Dean | November 29, 2007 9:26 AM
Thanks for this. The information I got was from an old account rep with VMware. I was interpreting from the slide I was given. This is apparently much better data. I'll keep researching.
Posted by: Greg Shields | November 29, 2007 2:32 PM