Microsoft Makes vSphere Look Like A Toy Once Again

Microsoft has increased the maximums once again for Hyper-V, with the upcoming release of Windows Server 2016. They’re leaving VMware not just in the dust, but somewhere so far behind that they’re over the horizon.

image

How does vSphere 6.0 stack up against the superior Hyper-V?

image

Ouch! Enjoy, vFanboys!

I can’t wait for the angry tweets!

4 thoughts on “Microsoft Makes vSphere Look Like A Toy Once Again”

  1. Honestly I don’t think many people are picking a hypervisor purely on the amount of memory and CPU supported but still it is great that MS are pushing the boundaries.

    I’ve run both Hyper-V (2012) and vSphere in my labs and both suck in terms of their usability, but I think Hyper-V was probably worse.

    The complexity and bloat of vSphere will be it’s downfall in my opinion. At least Microsoft have a route out with Azure.

    1. Oh you’re no fun! It seems like everyone misses the point completely. Yes, the numbers are meaningless. That’s how VMware are responding to this, just as they did when Microsoft announced their 2012 R2 figures. And then VMware marketing went mad when they announced their v6.0 figures, and they likely will again with their v6.5 or v7.0 figures.

      This whole thing is like which car is better, a Ferraro Enzo, a Pagani Zonda, or a Bugatti Veyron. I’ll never drive any of them, and I’d clock up enough points on my license in 10 minutes to ban me from the road if I even put one of them into 3rd gear! But that doesn’t stop the debates and the fun. And the same is true with hypervisor maximums. I don’t think we could justify a host with the above figures … but we could do it … at least with Hyper-V 🙂

  2. Biggest problem in Hyper-V is still management (!!) / troubleshooting and configuration.

    Nobody cares about higher numbers from both vendors, but VMware is still the more complete Hypervisor Environment.

    And – i’m truely not a VMware fanboy and would like to see MS to get this done 😉

  3. The problem i have with VMWare isn’t just the fact you have to learn yet another product (something many of my co-workers were unwilling to do), but you also have to shell out an awful lot of money, for something Windows can do out of the box. I’m tempted to say Microsoft made VMWare redundant (certainly for SME’s) after the release of Windows 2008R2.

Leave a Reply to Shaun Ritchie Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.