Windows 2012 Hyper-V is the hypervisor for the cloud. VMware’s vSphere is a dead man walking?
In parts One and Two I shared a chunk of what I learned from Aidan Finn‘s enlightening and entertaining session “Windows Server 2012 Hyper-V & VSphere 5.1 – Death Match” delivered at the E2E Virtulisation Conference in Hamburg. We’ve considered pricing, scalability and performance, as well as storage then gone on to consider resource management, security and multi-tenancy and what a flexible infrastructure can give.
Some have found this a useful comparison. Others have highlighted that this isn’t a feature-by-feature comparison and that if it was, the tables would be very different: they would, they’d be longer for a start. But more importantly, would they give the high view that many are focused on? Is the goal a technical Top Trump victory, or alignment to business goals? If aligned, how aligned? A friend used to often quote the difference between cabinet making, carpentry and joinery is effort and measurement: they each had their place, the trick was knowing what level to apply.
In Part III, lets question further Aidan’s premise that Hyper-V kills vSphere. Here we’ll consider High Availability and Resiliency.
Windows 2012 Hyper-V is the hypervisor for the cloud, VMware’s vSphere is a dead man walking?
In Part I I shared a chunk of what I learned from Aidan Finn‘s enlightening and entertaining session delivered at the E2E Virtulisation Conference in Hamburg tastefully titled, “Windows Server 2012 Hyper-V & VSphere 5.1 – Death Match”. In Part I we looked at pricing, scalability and performance, as well as storage in questioning how bold this statement was.
Pure license-cost wise, it more straightforward to run Microsoft Hyper-V than add another licensed hypervisor: note that Hyper-V does have a free offering (although this version doesn’t cover the virtual Windows Server instance licenses). We showed that scalability wise, Hyper-V can better common competition. Storage-wise Hyper-V, as should be expected from the newest offering, supports the newest technology: 4k sector sizes, and had the largest virtual disk support. Still, if you needed greater than 2TB of storage, you could always join multiple 2TB instances together, or bypass limits by mapping a LUN direct to the VM.
Still, besides pricing simplicity, performance improvements, and updated storage what has Microsoft done for the latest version of Hyper-V? In Part II, lets question further Aidan’s premise that Hyper-V kills vSphere.