Heterogeneous virtualization has been a hot topic among clients and last week at the Gartner Data Center conference in Las Vegas I presented a session on the subject. During the session, I polled the audience on their heterogeneous virtualization plans. Fifty participants responded to each polling question.
The first question I asked was about the current hypervisors that were deployed (note that the values are the number of respondents and not a percentage).
As you can see, most participants used VMware vSphere as expected, and there was a good mix of Hyper-V, XenServer, and some RHEV and Oracle VM.
It’s one thing to have multiple hypervisors, but not everyone is using multiple hypervisors to run production server applications in their data centers. That’s why I asked attendees which hypervisors they were using to run production server applications.
Notice that the drop was pretty significant. In the first poll, 44 non-VMware hypervisors were used. In the second poll, that number dropped to 25. The drop is consistent with an important but often unreported multi-hypervisor trend – while most organizations are using multiple hypervisors, most are not using multiple hypervisors for their production server applications (Oracle VM is a common exception). The second or third hypervisors deployed within an organization are often used to support branch office or departmental deployments. The fact that the additional hypervisors are being used is important, but so is understanding the use cases.
With that in mind, I also asked attendees about their plans for a single hypervisor.
Most (57%) planned to use a single hypervisor for production server workloads that required DR, with DR simplicity being the primary driver behind that decision. Clients frequently tell me that they fear that multiple hypervisors will recreate some of the same DR challenges that they initially solved with server virtualization. In addition, the OPEX concerns are real. Clients doing heterogeneous virtualization today almost always have a separate management silo for each hypervisor. When political or geographical issues preserve IT silos, the per-hypervisor silos might not be too big of a deal. However, organizations looking to be more centralized and efficient should aim for higher degrees of standardization.
Does this data mean that VMware wins? Not necessarily. I’ve had many calls with clients that are considering to switching to Hyper-V as their standard virtualization offering. That switch will take place over a 3-5 year period, with the end goal of having a homogeneous virtualization layer. If VMware is smart, it will focus on the OPEX and DR benefits of its homogenous solution, while still offering heterogeneous management throughout its stack to give customers choice. It’s clear that there is also plenty of interest in best-of-breed solutions as well, so opportunity exists for all vendors.
In 2013 we will spend a lot of time helping our clients unleash their inner service provider. That will involve taking some nontraditional approaches to data center standardization and optimization to help reduce TCO and improve efficiency and scalability. Stay tuned for more information on that subject.
What do you think? I’m curious to hear your plans around heterogeneous virtualization.
Read Complimentary Relevant Research
Cloud Computing Primer for 2017
Cloud has evolved from a disruption to an expected approach to traditional as well as next-generation IT. Our research helps IT leaders,...
View Relevant Webinars
Orchestrating Docker Container-Based Applications at Your Scale
Developers have fallen for Docker as a packaging and deployment technology, leaving infrastructure and operations teams dealing with...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.