Managing the hypervisor battle
Mar 10, 2009 Blogs
I’ve been reading up on loads of articles dealing with the differences and similarities between hypervisors. Lots of these articles compare different hypervisor performance-wise.
Here are some of the blogposts comparing hypervisors and/or management tools:
- Prestaties van Hyper-V, XenServer en ESX vergeleken
- VMware ESX slaat Hyper-V knockout
- Presentation: Hyper-V vs ESX in the datacenter
- Lab Experiment: Hypervisors
- Say it isn’t so: Hyper-V and XenServer outperform ESX
- Reaction to “Say it isn’t so: Hyper-V and XenServer outperform ESX”
- Lack of VMware Resource Pool awareness
- Destruction of VMware vCenter templates
- Botched management of VMware ESX port groups
- Unnecessary ISO image file proliferation
- PRO Tips not working as expected for ESX hosts
- Disconnect of VI Clients on SCVMM restart
- Manual cleanup required after SCVMM-VI3 integration
At work, I am responsible for all projects and initiatives handling virtualization. This includes (but is not limited to) VMware ESX and vCenter, Microsoft Hyper-V and SCVMM, Citrix XenServer en XenServer Essentials. I also train collegues to use these virtualisation solutions. Therefore, I need to be up to date on all the vendor’s products and solutions.
One thing that surprised me, is the ongoing battle between the hypervisors. Which is the fastest, which has the most complete feature-set? As you can read in the articles linked above and other resources on the web, it seems to be a big deal to compare Hyper-V (both the GA and the beta R2), VMware Infrastructure 3, VMware vSphere and Citrix XenServer.
As a techie, I really like these discussions, and like to replicate the situations and scenario’s described in these posts to check the facts and play around. As a VMware-enthosiast I still root voor ESX, although I do like to explore new possibilities with all the hypervisors out there.
As a manager virtualization, I don’t actually use or even care for these posts: I focus on the ‘higher-level’ comparisons, i.e. the management tools. I’ve been beaten to death with terms like ’single pane of glass management’, ‘unified management’, ‘multi-hypervisor management’, etcetera.
Both Microsoft, Red Hat and Citrix have announced and are working on ways to enable multi-hypervisor management for their respective tools.
Eric Gray over at VCritical has made an excellent post yesterday about this unified management thing: “Managing VI3 with SCVMM considered harmful“. Microsoft’s Rakesh Malhotra almost immediately responded with a rather hefty post: “SCVMM 2008 and VMware management – we must be doing something right…“. He attacks each and every single point Eric has reased in the last couple of months, comparing both hypervisors and management tools. Yesterday’s post covered Microsoft SCVMM’s ability to manage VMware Infrastructure environments, and concluded it is doing a poor job. Rakesh countered aggresively by concentrating more on the ‘manager of managers’ point of view.
I really enjoy these discussions about the management tools comparisons, as these will ultimately make the difference in choosing your virtual environment. My point with this post is actually to warn all of those tech guys out there for the temptations of single pane of glass management. You will find that using a single pane of glass management system will almost always decrease the functionality, but will increase the manageability.
So if you don’t care about the loss of some functionality (like templates when managing VI3 with SCVMM), go with the flow and hype up your virtual infrastructure using unified multi-hypervisor management. If you’re interested using your environments to the fullest, get used to having both the VIClient and SCVMM opened on your workstation to get the job done.
My opinion: if you’re paying for it, use it. I categorize myself in the latter group, caring more for full functionality (for which I’ve paid good money) instead of having just one view of the complete environment. Paying extra to lose functionality just doesn’t seem right to me.
March 12th, 2009 at 23:38
Great post Joep, I just don’t completely share your opinion. First of all I expect to see more and more mixed hypervisor environments, because different hypervisors have different advantages and disadvantages.
Now I do agree that the multi-hypervisor tools are not at the point where they should be, but these tools are only the first step in this direction and will become better and more feature rich. Now even if some features aren’t available in these tools they enhance the managebility of your environment. So per environment there should be an assesment if the missing features are essential and if not i can see administrators choosing the multi-hypervisor managementtool.
I’m also wondering if you have had time to investigate Citrix Essentials for managing Xenserver and Hyper-V
March 13th, 2009 at 0:59
Hi Niels, thanks for your reaction. At this point, the sad thruth is that using SCVMM for managing vCenter/ESX will not only cost you extra (having two management tools instead of one), but will make your environment more complex: some tasks can be done in SCVMM, others have to be done directly in vCenter. How is something more expensive and not feature-complete beter?
I’ve been playing with Citrix XenServer Essentials, and plan to write about it next week.
March 13th, 2009 at 1:07
Hi Joep, i’m not saying IT departments should buy SCVMM to manage their vCenter/ESX environments. But in a mixed environment Hyper-V and ESX i personally see the advantages of consolidating management to one tool even if it may cost some features.
March 13th, 2009 at 11:34
Well, obviously, the single pane of glass thing is a great idea, to minimize management overhead. I would applaud any management tool that fully manages multiple hypervisors.
At this point in time, however, none of the management tools offered today are capable of managing multiple hypervisors in any good sense, so I do not see why anyone would pay extra for management software to actually lose some of the features of the individual hypervisors.
March 13th, 2009 at 15:25
You keep talking about extra cost, but in any half decent Hyper-V environment you’ll need SCVMM, so i don’t see how using this tool in a mixed environment would cost you extra.
Same goes for environments with Xenserver where you’ll need to have Citrix Essentials.
March 14th, 2009 at 7:03
Joep, nice article. It would be great to see more coverage of virtualization management. Not as “cool” as the hypervisor, but each needs the other.