Posted by: Colin Steele
Colin Steele, Hyper-V vs. VMware
The July 2009 release of Microsoft Hyper-V R2 came with a lot of hype.
In some corners, VMware was still the successful little engine that could, and Microsoft was the giant locomotive that would run it off the tracks — just like it had against Netware, Netscape, Lotus and others. But here we are 15 months later, and that vision isn’t even close to reality.
Thomas Bittman, Gartner vice president and distinguished analyst, wrote this week that “Hyper-V is under-performing” and questioned if his expectations for Microsoft were too high. Clearly they were, and he’s not the only one to make that mistake (present company included).
Just take a look at the results of our “Virtualization Decisions 2010 Purchasing Intentions Survey.” Microsoft’s overall market share numbers may be up, but the company actually lost ground in its battle for virtualization supremacy. Last year, when we asked people to identify their primary server virtualization platform, 67% said VMware and 12% said Microsoft. This year, VMware jumped to 76% and Microsoft only went up to 13%.
By combining analysts’ market figures and our survey results, you can assume that most Hyper-V adoption is taking place in existing VMware shops. (If Microsoft’s overall market share is going up, but the percentage of Hyper-V-first shops is staying the same, that means the increased adoption is taking place in shops that don’t primarily use Hyper-V.)
That’s not a good sign for Microsoft. The “get a foot in the door and convert VMware customers” approach isn’t going to work. Most users aren’t going to rip and replace their entire VMware infrastructure, unless they’re really, tremendously, super-duper-unhappy with it.
As Bittman wrote, the thought was that Hyper-V R2 would attract midmarket customers that hadn’t virtualized much (if any) of their infrastructure. That way, Microsoft’s market share would grow, and more users would identify Hyper-V as their primary platform.
But that hasn’t been the case, and there’s no sign that Microsoft — even with Dynamic Memory in the upcoming Hyper-V R2 SP1 — will be able to change that.