VMware has a fling with Microsoft Hyper-V support

analysis
Feb 28, 20115 mins

VMware changes direction and allows its vCenter XVP Manager and Converter plug-in to manage non-vSphere hypervisor platforms

VMware administrators seem hard-pressed to give up on using VMware vCenter Server to manage their virtual data centers. That’s been good news for VMware, as the company expands its virtualization management software stack.

But if these virtualization shops continue to mix other hypervisor platforms into their environments, virtual administrators may have no choice but to invest in third-party management tools in order to maintain control over a growing heterogeneous hypervisor infrastructure. They may even start giving Microsoft System Center Virtual Machine Manager (SCVMM) more consideration, which would probably get under VMware’s corporate skin pretty quick.

[ Will Dell, HP, and IBM focus on creating their own virtualization management tools or will they create plug-ins to VMware vCenter? | Also on InfoWorld: Is VMware vCloud Director the new VMware Lab Manager? ]

Thanks to a bit of VMware vExpert sleuthing back in October 2010, we speculated that VMware could be planning to support Microsoft Hyper-V and Xen virtualization hypervisor platforms in some form or fashion. Now, only four months later, speculation has turned into reality.

VMware Lab engineers have pushed out a new and useful plug-in tool for the VMware community. This is the group responsible for creating interesting tools, dubbed “flings,” which are intended to be free, short-term solutions. VMware says these types of tools are intended to be played with and explored, but that they do not come with VMware support and therefore shouldn’t be used in your production environment.

This latest fling is called vCenter XVP Manager and Converter, and it’s described as providing “basic virtualization management capabilities for non-vSphere hypervisor platforms towards enabling centralized visibility and control across heterogeneous virtual infrastructures.” In other words, users can manage competitor hypervisors and VMs from within their vSphere Client. But according to the system requirements of this particular fling, it appears it currently only supports Microsoft virtualization technologies, specifically:

  • Microsoft Hyper-V Server 2008
  • Microsoft Hyper-V Server 2008 R2
  • Windows 2008 (64 Bit) Hyper-V Core (including Standard, Enterprise, and Datacenter Editions)
  • Windows 2008 (64 Bit) Hyper-V Full (including Standard, Enterprise, and Datacenter Editions)
  • System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2

vCenter XVP Manager includes both a server and client component. The server component is installed on its own physical server or in a virtual machine while the client component is installed as a plug-in with vSphere Client. The plug-in for the vSphere Client is what keeps the VMware administrator true to VMware’s management software, because it provides the administrator with the familiar VMware interface while still being able to manage competitor virtualization platforms and VMs.

Keep in mind, however, that this fling is still an unsupported Technical Preview, and it doesn’t offer the full functionality of vSphere vCenter Server management to Microsoft Hyper-V hosts and virtual machines. Instead, the current set of operations are very basic; fortunately, it does support the more commonly used day-to-day management functions. For example, it offers:

  • Inventory management. Provides administrators with the ability to add non-vSphere hosts to the vCenter inventory and remove them from the inventory. It also allows for the creation and deletion of new virtual machines on non-vSphere hosts.
  • Host management. Provides a configuration summary view and a resource utilization summary view of non-vSphere hosts; provides remote console access to non-vSphere hosts; enables simple power operations on non-vSphere hosts.
  • Virtual machine management. Provides a configuration summary view and resource utilization summary view of non-vSphere virtual machines. Provides remote console access to non-vSphere virtual machines. Enables power operations on non-vSphere virtual machines as well as guest operating systems running within them (power off, power on, suspend, shut down the guest and reset). Allows modification of virtual hardware settings associated with non-vSphere virtual machines (such as changing the amount of memory or the number of vCPUs, or adding/removing a floppy drive, CD drive, hard drive or network adapter).
  • General infrastructure. Displays tasks initiated on and events associated with non-vSphere hosts and virtual machines within the general tasks and events pane.

Even though VMware appears to be bending a bit by offering management of competitor hypervisors within its own management application, they aren’t exactly giving up the hypervisor fight.

This fling does more than heterogeneous hypervisor management. It also adds a virtual-to-virtual (v2v) image conversion technology into the mix that claims to simplify and enable easy migrations of virtual machines from non-vSphere virtualization platforms to VMware vSphere formats. So while VMware provides you with a way to see and interact with your Hyper-V VMs, the company also gives you an easy method of clicking on that same VM and converting it to a vSphere format. Do that enough times, and you’re back to a homogeneous VMware environment.

VMware has been downplaying other virtualization platforms like Hyper-V and Xen for years now, never really giving them credence or acknowledging them as any significant threat. But actions often speak louder than words. By adding support for other hypervisors — even as a fling that may never see the light of day as an official product — VMware finally seems to be legitimizing the competition.

Analysts may be projecting Microsoft and Citrix hypervisor market share growth, but I don’t think these numbers are really what concern VMware. This move seems to be less about hypervisor market share and more about virtualization management market share. If someone wants to dabble with another hypervisor platform within a VMware-dominated virtual data center, the virtualization giant can probably stomach that. But what they don’t want to live with is that same administrator spending his management software budget elsewhere on some heterogeneous third-party product.

If you want to get your hands on this latest fling or any of the other experimental flings currently available, check out the VMware Labs website and start downloading them now.

This article, “VMware has a fling with Microsoft Hyper-V support,” was originally published at InfoWorld.com. Follow the latest developments in virtualization and cloud computing at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.