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.
Windows 2012 Hyper-V is the hypervisor for the cloud, and VMware’s vSphere is a dead man walking. So declared Aidan Finn at a recent virtualization conference in Hamburg during an enlightening entertaining session which he tastefully entitled, “Windows Server 2012 Hyper-V & VSphere 5.1 – Death Match”.
A bold statement? Hyper-V has often been cited as a “nearly ran”; good enough for the SMB space and smaller Private Clouds, but lacking the muscle for a cloud-focused enterprise. Nice for a visit, wouldn’t want to live there.
In terms of embedded services and experience, VMware’s vSphere has a significant place in many organisations’ data centres. Licensing alone is unlikely to change hearts and minds to convert, but what about features?
Can Microsoft claim that Hyper-V is the hypervisor for the cloud? What new features are available in the 2012 release, and how does it now compare to vSphere 5.1. More importantly, will these changes drive wider adoption?
In this first installment, we take a look at pricing, scalability, and performance, as well as storage.
There was an amount of kerfuffle when VMware released vSphere v5.0 and moved to a memory centric licensing model. We speculated on whether other vendors would follow suit. Microsoft has unveiled Windows 2012 licensing terms, which it claims make licensing simpler and better value . The thing to commit to memory? There are now only four versions, and licensing is processor and client access license based.
VMware has made it known for quite some time that virtualization, private clouds (IT as a Service), hybrid clouds, and public clouds will create the need for a new management stack, and that VMware intends to be an aggressive supplier of such a new management stack. However, what VMware has never before said is precisely what would be different about this new management stack (other than it explicitly supporting vSphere) than all of the other management stacks that have existed for all of the other computing platforms in the world.