Microsoft Hyper-V 3.0 compared to VMware vSphere 5
January 29, 2012 12 Comments
Update: August 20, 2012
Update September 4:
I made a new feature compare of Windows Server 2012 Hyper-V RTM edition and VMware vSphere 5.1.
Read it here.
In August 2012 I added a couple of new postings in which is given more details on subjects of vSphere and Hyper-V.
vSphere 5 versus Windows Server 2012 Hyper-V: storage integration
vSphere 5 versus Windows Server 2012 Hyper-V:management
vSphere 5 versus Windows Server 2012 Hyper-V: high available VMs
vSphere 5 versus Windows Server 2012 Hyper-V: Resource metering for chargeback
vSphere 5 versus Windows Server 2012 Hyper-V: costs
vSphere 5 versus Windows Server 2012 Hyper-V: hybride cloud
vSphere 5 versus Windows Server 2012 Hyper-V: live migrations
vSphere 5 versus Windows Server 2012 Hyper-V: high available VMs
Microsoft Hyper-V 3.0 promises to offer a lot of new features. Microsoft itself says in this posting on technet.com
‘ The upcoming Hyper-V 3.0 release that’s included in the next version of Windows Server has closed the technology gap with VMware’s vSphere’
We all know Microsoft is very good at marketing and we also (should) know currently Hyper-V 2.0 is far behind vSphere 5 when looking at features, scalability and enterprise readiness. Also until Windows Server 2012 is generally available (GA), we will not know for sure which advertised features will be part of the GA version.
Public and private clouds are in my opinion the IT of the future. Microsoft and VMware both have solutions which enable a cloud computing infrastructure. Please also read my blogposting titled Mythbusting:Can a VMware private cloud cost 5 to 16 times more than Microsoft private cloud? to learn about the offering on private cloud.
I decided to do some research on all the new features of Hyper-V 3.0 and compare it to the feature set of vSphere 5. I did this unbiased. Unlike Microsoft and VMware, who tend to only mention features the competition does not offer I try to mention all relevant features in this posting and future updates. If you have additions or feel features are not correct please let me know. If needed I will adjust the overview. Sent a short note to my email address mvdb22 (at) gmail dot com.
The image below shows the features of VMware vSphere 5 Enterprise Plus edition compared to Hyper-V 3.0 as far as I could find out using documentation on the internet.
To show the progress Microsoft has made I also list the current features of Hyper-V 2.0.
The information on features is based on the Windows Server 2012 Release Candidate.
Click on this link to view a table showing features of vSphere 5 standard, enterprise and enterprise plus and Hyper-V 2.0 and Hyper-V 3.0
Features and license costs are quite easy to compare. But there is more to consider when selecting which solution best fits the demands and budget. This posting provides an overview of several aspects performance, eco-system, reliability, guest support.
Cost of licensing
There is always a lot of focus on costs. Costs have two aspects: the cost in buying something (CAPEX) and the costs for operating something (OPEX).
It is pretty clear that Hyper-V is and will be cheaper than vSphere. Mind the vSphere Essentials Plus edition combined with offers from Veeam are compatative to Hyper-V in cases where no more than three hosts are needed.
While comparing CAPEX is pretty easy, comparing OPEX is difficult. How can you tell that management of a Hyper-V environment will cost more or less effort (=time) than managing a vSphere environment?
However, seeing the big price difference and growing number of features in Hyper-V 3.0 it will be more difficult to convince your boss to start using vSphere instead of ’free’ Hyper-V.
Large enterprises (which all use server virtualization for some time) will not rapidly change to Hyper-V for production. Maybe they do Proof of Concepts or start using Hyper-V in Test/Dev infrastructures.
Several benchmarks do not show a significant performance difference between Hyper-V and vSphere.
While smaller infrastructures can do well with just a hypervisor and management, enterprises will need a lot of additional tooling to be able to manage the virtual infrastructure efficiently. VMware is a clear winner here. There are lots of third party solutions supported on vSphere for functions like backup, performance monitoring, disaster recovery, management, virtual appliances etc etc.
Also lots of hardware vendors offer solutions for vSphere.
Microsoft itself has a growing number of solutions part of the System Center Suite to manage both the physical and virtual infrastructure. The eco-system is growing with solutions like Veeam Backup & Replication for Hyper-V backup.
A vSphere private cloud can easily integrated with a public cloud based on vSphere using vCloud Director. In the near future virtual machine can be vMotion-ed form private cloud to public cloud and reverse.
Microsoft has some integration between a private cloud and Azure public cloud using the new System Center App Controller 2012. This software delivers self service for deploying services to either private or public cloud instead of management which vCloud Connector delivers. In June Microsoft announced Azure which used to be a PaaS platform will also support virtual machines. So customers can upload their VHD files to Azure and run there.
For a public cloud additional tooling is needed. Both Microsoft System Center 2012 and VMware software like vCloud Director and vCenter Operations Management Suite offer the ability to build and operate a private cloud.
Microsoft does not offer a chargeback tool like VMware does with Capacity IQ. Also on Lifecycle management and Capacity Management limited functionality is delivered by System Center 2012 products.
Also Microsoft offers limited security solutions between virtual datacenters. VMware has a range of solutions in the vShield family.
SCVMM 2012 combined with Server App-V allows to automatically deploy both virtual machines and server applications like SQL and Internet Information Services.
Microsoft System Center Suite 2012 is licensed per CPU socket in the host while VMware solutions are mostly licensed per VM (vCenter per instance). In most if not all cases VMware has a more expensive solution but delivers a lot of out of the box functionality.
Microsoft did a lot of work on scalability. More servers can be part of a cluster and larger servers are supported now. I believe Hyper-V 3.0 and vSphere are quite equal on this. vSphere is still limited to 2 TB virtual disk files which can be an issue for fileservers and databases. Hyper-V 3.0 has a virtual disk size limit of 64TB when using the new VHDX format.
One of the weak spots of Hyper-V 2.0 is storage. Clustered Shared Volumes can have some issues especially when backup are running. Most can be solved by installing hotfixes. Hyper-V 2.0 and SCVMM 2008 do not feel as reliable and robust as ESX and vCenter Server does.
During demos of the Developers Preview of Windows Server 8 and Hyper-V 3.0 I heard some complains about the reliability. We will just have to wait and see how this evolves when Windows Server 2012 is released and get experience.
While vSphere clearly has a lot more memory techniques which enables a higher consolidation rate on the hosts, it can be argued if this justifies the much higher licensing cost of vSphere. Also internal memory is not that expensive anymore.
vSphere supports a wide variety of guest operating systems. If you are running different Linux os or even Netware this is an important feature.
There are a few other non vendor blogposting which compare vSphere and Microsoft Hyper-V 3.0.
Read Erik Scholten (experienced in VMware vSphere) view on Hyper-V 3.0 compared to vSphere.
Read Steve Beaver (VMware vExpert ) opinion in his blog on Virtualizationpractice.com
Hyper-V 3.0 with Windows Server 2012 and System Center 2012 are going to deliver a lot of value for a relative low price (license) compared to VMware’s solutions. We will have to see how VMware responds. My guess is that prices will drop, vRAM entitlements will be increased or other deals will be offered to lure new VMware customers and prevent current customers from moving to Hyper-V. This could happen end of 2012/begin of 2013.