VMware ESXi vs Microsoft Hyper-V: which one is better for SMBs?
Today VMware hit another major step towards the hypervisor’s commoditization by releasing its bare-metal hypervisor ESX for free.
And this move, planned long time by the former CEO Diane Greene, is clearly a move to counter the raising menace of Microsoft and its new free hypervisor Hyper-V.
Now that both players are targeting the SMB market (while Citrix is fully busy challenging VMware in the Enterprise space), one interesting question to answer is: which product is better?
As the history tells us better doesn’t necessarily means with most features, as the product positioning involves the sales channel capability to win the customers, the total cost of ownership, the capability to scale up with the company, the hardware and software support for the ecosystem, etc.
While these factors are hard to measure, the TCO has a special appeal and no company cannot avoid the temptation to calculate the hidden costs of the competing offerings.
The first attempt comes from VMware, thanks to Mike DiPetrillo, the now popular Specialist System Engineer of Industry Research and Competitive Analysis department, that uses his personal blog to detail a pretty interesting analysis:
…
Everyone out there has a different view on what the SMB space is made up of but pretty much everyone agrees that they have fewer than 50 servers and a minimal IT staff that's mostly educated on Microsoft products. I know there are exceptions but I'm going for the larger group here.
With any of today's virtualization solutions and a half way decent 2 socket system you should be able to get at least a 10:1 consolidation ratio and probably closer to 15:1.
…
ESXi 3.5 is completely free. The Hyper-V role is completely free. The major difference is Hyper-V requires a Windows Server 2008 host to run and ESXi 3.5 does not. Most SMBs out there do not pay for Software Assurance (Microsoft's upgrade program) for their server software. I don't have any hard stats so if someone does please reply in the comments section. I'm just going off my experience of selling to this space for a very long time. This means that you have a lot of SMBs out there running Windows Server 2003 or even Windows Server 2000 or Windows NT. Since you need Windows Server 2008 in order to run Hyper-V this means you have to go out and pay for the cost of a Windows server license just to get Hyper-V.
…
Let's say you decide after adding the 3 hosts it would take for your 30 VM environment that you want to have some centralized management capabilities. In the Hyper-V world that means Systems Center Virtual Machine Manager. In the VMware world that means Virtual Center Server. Again, this is not a feature comparison article. Both solutions at their basics allow for the same things - create and manage a VM, manage a library, one pane of glass, etc.
…
So, just to recap on the 3 host, centralized management solution - Microsoft SCVMM = $3,300 buying a la carte or $499 for the Workgroup Edition (we'll use Workgroup for our final tally numbers); VMware VI Foundation = $2,995.
…
It's worth mentioning that when you buy VMware Foundation you get some nice advanced features in the bundle such as VMware Update Manager (patching of hosts and VMs) and VMware Consolidated Backup. If you wanted similar features for Hyper-V you would need to buy the Systems Center Systems Management Suite Enterprise (SMSE) which costs $1,290 per host.
…
Now we're looking at the advanced features such as patch management and backup for our 3 host solution - Microsoft with SMSE = $4,260; VMware VI Foundation = $2,995.
…
DiPetrillo closes with a comparison table:
| Microsoft Hyper-V | VMware ESXi | |
| Basic Consolidation | $3,000 | Free |
| Centralized Management | $3,500 | $2,995 |
| Backup & Patching | $7,260 | $2,995 |
Some of the points in this analysis may be arguable.
For example the virtual infrastructure patching can be achieved through the great WSUS, a product that Microsoft releases totally free or charge.
Nonetheless this analysis highlights an important point: to perform a basic and critical feature like virtual machines backup, Microsoft today obliges the customers to buy Data Protection Manager (no matter if it’s included in the SMSE bundle).
This happens because NTBackup, which is included in every copy of Windows and it’s ready to do the much wanted live snapshot through the Volume Shadow Service (VSS), can’t run the job.
Microsoft had the opportunity to use NTBackup as a competitive advantage against VMware and didn’t use it.
As usual we’ll update the post with any relevant answer from Microsoft and others.
Update: While Microsoft still refrains from arguing this cost analysis, at least a couple of prominent figures in the virtualization world have something to say about it.
Chris Wolf, Senior Analyst at Burton Group, changed the requirements to include high-availability (a much savvy choice) and extended the comparison to Citrix and Virtual Iron. He found out that Microsoft is significantly less expensive than VMware.
Massimo Re Ferrè, IT Architect at IBM, proceeded exactly in the same way, adding high-availabiliy as a mandatory requirement, and found out the same thing: Microsoft is less expensive than VMware.
25 Comments
Anonymous
Monday, July 28, 2008 8:16:00 PM
If you buy 3 1 socket quad core servers that would be 9000.
However, datacenter includes unlimited virtualization.
Thats mean you could run 30 copies of Windows Server 2008 for 0$ more than the costs of 3 copies of Datacenter.
ESX would require 30 copies of Windows Server 2008. Standard Edition with 5 CALs each would be 30,000$.
There is no coupling between the entitlements that Datacenter gives you to run multiple instances of itself in a virtual environment and the underlying Hypervisor. I believe they had some coupling there originally, however it was very quickly removed and is not there today.
Therefore, I would argue that there is no coupling between the Host and Guest purchasing decisions. With either product you can make those decisions independently.
Where things get complicated is that Microsoft has not released their Hyper-V only version of Server 2008 yet (going to give away just the Hyper-V role for $28), hence you need to buy a full version of Windows today to get the role. If you want features like "Quick Migration", you need Enterprise or DataCenter for the clustering services. So, they fact that you have been forced to buy an OS for your virtualization might influence some of your guest decisions. However if you felt that there was a benefit in running enterprise, then you could purchase that as a guest in the VMware case. In most cases as the author points out, they aleady have the guest licenses and just want to virtualize further strengthening the argument that you can de-couple the discussions. Not saying there is a total de-coupling, however I think they can be sufficiently separated for the purpose of this discussion.
http://www.evolvetech.com/mambo/index.php?option=com_myblog&show=Is-VMWare-cheaper-than-Microsoft-.html&Itemid=87
We focus on SMB solutions, and the products Mike chooses to look at are not the natural selections for the SMB.
Dave Sobel
CEO
Evolve Technologies
Also, you can downgrade the "free" guests.
"The use rights also allow the choice of running Windows Server 2008 (or previous version) Standard, Enterprise, and Datacenter in the virtual instances."
You dont need VMM to manage Hyper-V you can use powershell or the mmc snaping from another computer (but you need VC for manage all features for ESXi)
In the near future you can buy W2K8 Hyper-V for 28$.
In order to have ESXi you will have to buy new hardware, but you can use Hyper-V on you already have 64x hardware.
And, what about support,etc?,
SMB and you use Datacenter?, for SMB enterprise that allows you to use 1 licences in host and 4 guess for free, it would be enought.
http://blogs.technet.com/m2/archive/2008/04/17/invoking-diskshadow-to-back-up-a-virtual-machine-from-a-hyper-v-host.aspx
And it will speak with VSS providers inside the VM in order to obtain a valid state of Exchange, SQL, etc.
An ESX host can be managed through a web browser. VC is not required.
Also, totally agree with you that hardware compatibility is more restrictive with ESXi than Hyper-V (I actually think this is a good thing if you are considering running 10 guests on a single physical piece of hardware. I feel better knowing it has been rigorously tested). However, people could read into your post that Hyper-V does not require new hardware. Its requirements for an x64-based processor, hardware-assisted virtualization, and hardware data execution protection would not be without its fair share of people that find themselves needing to upgrade either.
ESXi can run on more hardware than VMware states. They just haven't tested it yet.
Hyper-V simply doesn't run as efficiently, or as stable as esx(which duh, has had a lot more time in the oven).
I'll wait until they are at version 2 or better, because thus far it's not worth it if they were giving it away for free.
many VARs can now get a boost of work.
they come to a 3-10 servers + storage farm and say "for $6000 i'll convert all your servers and put them on a big new machine and you'll be virtual next week"
businesses will return the investment on electricity savings alone.
We are also an ESX shop, but I haven't tested it on my XPS 420 because it won't install.
Perhaps you need a scsi controller, as ESX doesn't support every run of the mill sata drive and controller, otherwise it would be as bloated as windows, and much less efficient.
This is obviously VM-Ware biased as usual.
Minor correction: an ESXi host cannot be managed via web interface. It has a web interface but there is no management from it. However, from that web interface you can download the Infrastructure 2.5 client, which you use to connect directly to the host (instead of a VC server). It's kind of a pain for multiple hosts but works well enough for small deployments.
Daniel
We had ESX up in running in less than a half an hour, with no experience, first install.
> ...
Wow, you summed up our experience of Hyper-V perfectly. So much for disregarding advice about half-baked products. You get what you pay for, unfortunately, with this case, it looks like we ended up paying more for what seems a far inferior product.
You will need to licensed the guests OS. And the ESXi, you will need to make sure to verify the pricing per socket:
http://www.vmware.com/files/pdf/vi_pricing3.pdf
In terms of support, you will need to review the options Microsoft Provides you (which have different SLAs) and obvisouly costs:
http://www.microsoft.com/services/microsoftservices/srv_enterprise.mspx
and the comparison of without a glitch vs issues, it maybe a case of lack of training or knowledge in the tool.
the technical resource center is at:
http://www.microsoft.com/servers/hyper-v-server/technical-resources.mspx
You cannot buy one single license of that product.It in the license agreement so it will be more expensive than you think.
Thanks.
Add New Comment
Copyright © 2003-2009 virtualization.info. All rights reserved.
virtualization.info Network: virtualization.info | virtualization.tv | Virtualization Congress

