VMware

VMware vCenter Multi-Hypervisor Manager 1.1
Release Notes


VMware vCenter Multi-Hypervisor Manager 1.1 | 25 Apr 2013

Build 1100332 | Product Download

Last Document Update: 22 Sep 2013

Check frequently for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

The vCenter Multi-Hypervisor Manager 1.1 release notes provide information about VMware vCenter Multi-Hypervisor Manager, an optional module for VMware vCenter Server. For information about vCenter Server features, requirements, and installation, see the VMware vSphere Release Notes.

For more information about vCenter Multi-Hypervisor Manager, see Installing and Configuring vCenter Multi-Hypervisor Manager and Managing Multi-Hypervisor Environments with vCenter Server.

Top of Page

What is VMware vCenter Multi-Hypervisor Manager 1.1

VMware vCenter Multi-Hypervisor Manager is a component that enables support for heterogeneous hypervisors in VMware vCenter Server. It provides the following capabilities to your virtual environment:

  • An integrated platform for managing VMware and third-party hypervisors from a single interface.
  • A hypervisor choice for the different business units in your organization to accommodate their specific needs.
  • No single hypervisor vendor lock-in.

When you add a third-party host to vCenter Server, all virtual machines that exist on the host are discovered automatically, and are added to the third-party hosts inventory.

The ability of vCenter Multi-Hypervisor Manager to migrate virtual machines from third-party hosts to ESX or ESXi hosts is implemented by exposing the capabilities of vCenter Converter Standalone in the vSphere Client. See VMware KB article 2048927 for information about dependency between vCenter Multi-Hypervisor Manager and vCenter Converter Standalone.

Top of Page

Key Capabilities

vCenter Multi-Hypervisor Manager 1.1 introduces the following set of basic management capabilities over third-party hosts:
  • Third-party host management including add, remove, connect, disconnect, and view the host configuration.
  • Ability to migrate virtual machines from third-party hosts to ESX or ESXi hosts.
  • Ability to provision virtual machines on third-party hosts.
  • Ability to edit virtual machine settings.
  • Integrated vCenter Server authorization mechanism across ESX/ESXi and third-party hosts inventories for privileges, roles, and users.
  • Automatic discovery of pre-existing third-party virtual machines
  • Ability to perform power operations with hosts and virtual machines.
  • Ability to connect and disconnect DVD, CD-ROM, and floppy drives and images to install operating systems.

Top of Page

What's New

The VMware vCenter Multi-Hypervisor Manager 1.1 is a minor release that introduces the following new capabilities:
  • Migration of virtual machines from Hyper-V to ESX or ESXi hosts.
  • Support for the latest Microsoft Hyper-V hypervisor (as well as earlier Hyper-V versions).
  • Increase in the number of supported third-party hosts to 50 from 20 in vCenter Multi-Hypervisor Manager 1.0.
  • Ability to manage custom certificates for the vCenter Multi-Hypervisor Manager server from the installer wizard.
  • Ability to select multiple objects in the UI of the vCenter Multi-Hypervisor Manager plug-in and a number of other usability improvements.
  • Ability to generate vCenter Multi-Hypervisor Manager log bundle from Windows Start menu.
  • Bug fixes.

Top of Page


How to Obtain vCenter Multi-Hypervisor Manager

You can download vCenter Multi-Hypervisor Manager for vCenter Server from the Download VMware vSphere 5.5 page here. Click View Download of a VMware vCenter Server 5.5.0 product line, and scroll to the bottom of the page.
To use the latest migration feature of vCenter Multi-Hypervisor Manager, you need to download and install a supported version of VMware vCenter Converter Standalone from here.

Top of Page


VMware vCenter Multi-Hypervisor Manager Security

VMware vCenter Multi-Hypervisor Manager supports HTTPS secured communication between the following components:

  • vCenter Server
  • vSphere Client
  • vCenter Multi-Hypervisor Manager server
  • vCenter Multi-Hypervisor Manager client plug-in
  • Third-party hosts

For more information about the connections between the different components, see Managing Multi-Hypervisor Environments with vCenter Server.

vCenter Multi-Hypervisor Manager supports both self-signed and third-party-signed certificates in the following manner:

  • Self-signed certificates must be accepted manually.
  • Third-party certificates are verified automatically by third-party authorities.

The vCenter Multi-Hypervisor Manager Server leverages the industry standard authorization mechanism of vCenter Server and propagates it over the inventory objects of both VMware and third-party hosts. You should use the vCenter Server integrated authorization instead of a third-party one.

Top of Page

Hardware Requirements

The minimum requirements to ensure acceptable vCenter Multi-Hypervisor Manager performance are as follows:

  • Processor: 64-bit processor with two or more logical cores, each with a speed of 2GHz.
  • Network: LAN
  • Storage: 1GB minimum
  • Memory:
    • Additional 2GB RAM on top of the memory hardware requirements for vCenter Server, if vCenter Multi-Hypervisor Manager and vCenter Server are installed on the same machine.
    • 4GB RAM if vCenter Multi-Hypervisor Manager and vCenter Server are installed on separate machines.

Top of Page

Installation Notes

The vCenter Multi-Hypervisor Manager module consists of a server component and a client component. The client component is a plug-in to the VMware vSphere Client. The vCenter Multi-Hypervisor Manager is distributed as a Windows installable package, which deploys the VMware vCenter Multi-Hypervisor Manager service. After installing the vCenter Multi-Hypervisor Manager server component, you have to install the vCenter Multi-Hypervisor Manager plug-in for the vSphere Client.

Consider the following when installing vCenter Multi-Hypervisor Manager:

  • vCenter Multi-Hypervisor Manager 1.1 is compatible with vCenter Server 5.1.x and 5.5 and vSphere Client 5.1.x and 5.5. It is not available in the vSphere Web Client.
  • You should install the vCenter Multi-Hypervisor Manager server on the same machine where vCenter Server runs. Alternatively, if you use a vCenter Server virtual appliance, which is Linux-based, you must install the vCenter Multi-Hypervisor Manager server on a separate Windows machine, as it is a Windows service only.
  • To benefit from the VMware vSphere High Availability feature, you can install the vCenter Multi-Hypervisor Manager server on a virtual machine.
  • You must associate each installation of vCenter Multi-Hypervisor Manager with a single vCenter Server instance.
  • To use the virtual machine migration feature of vCenter Multi-Hypervisor Manager, you must download and install VMware vCenter Converter Standalone.

The vCenter Multi-Hypervisor Manager server stores its configuration data in XML files located in its installation directory. The vCenter Multi-Hypervisor Manager server uses the vCenter Server database to store tasks, events, privileges, roles, etc. For more details, see the vCenter Server supported database formats.

If your vCenter Server 5.1.x or 5.5 system is licensed with vCenter Server Standard edition, you can download vCenter Multi-Hypervisor Manager without additional charge. The vCenter Multi-Hypervisor Manager is not available with the vCenter Server Foundation or Essentials editions.

For detailed information about installing vCenter Multi-Hypervisor Manager, see Installing and Configuring vCenter Multi-Hypervisor Manager.

Top of Page

Interoperability and Software Requirements

Supported Hypervisors

  • Microsoft Hyper-V Server 2012
  • Microsoft Hyper-V for Windows Server 2012
  • Microsoft Hyper-V Server 2008 R2
  • Microsoft Hyper-V for Windows Server 2008 R2
  • Microsoft Hyper-V for Windows Server 2008

Operating Systems that Support Installation of the vCenter Multi-Hypervisor Manager Server

The vCenter Multi-Hypervisor Manager server can be installed on Windows operating systems that vCenter Server 5.1.x and 5.5 supports.


For a list of the supported Windows operating systems, see the VMware Compatibility Guide.

Supported Guest Operating Systems

The vCenter Multi-Hypervisor Manager server is not a hypervisor by itself but a component that connects third-party hypervisors to the vCenter Server. It inherits the supported guest operating systems from each specific underlying hypervisor.

Interoperability between the vCenter Multi-Hypervisor Manager and the vCenter Server, vSphere Client, and vCenter Converter Standalone

To view information about the vCenter Server, vSphere Client and vCenter Converter Standalone versions that the vCenter Multi-Hypervisor Manager is compatible with, select the Solution Interoperability option of the VMware Product Interoperability Matrix.


Top of Page

vCenter Multi-Hypervisor Manager Support

vCenter Multi-Hypervisor Manager is a fully-supported vCenter Server feature. VMware provides support for all vCenter Multi-Hypervisor Manager or vSphere related issues. If you encounter issues with the underlying third-party hypervisors platform, VMware can only suggest workarounds or configuration changes, but the actual problem resolution must come from the third-party hypervisor vendor. For Hyper-V hosts, this is Microsoft Corporation.

Top of Page

Frequently Asked Questions

For a list of frequently asked questions about vCenter Multi-Hypervisor Manager, see VMware KB 2037570.

Top of Page

Resolved Issues

  • The vSphere Client might display the vCenter Multi-Hypervisor Manager server as disconnected
    When you restart the vCenter Multi-Hypervisor Manager server, the vSphere Client might display the vCenter Multi-Hypervisor Manager server as disconnected even after the server comes back online.
    Workaround: Restart the vCenter Multi-Hypervisor Manager plug-in. To restart the vCenter Multi-Hypervisor Manager plug-in, perform the following steps:
    1. In the vSphere Client, click Plug-ins and select Manage Plug-ins.
    2. Right-click VMware vCenter Multi-Hypervisor Manager, and select Disable.
    3. Right-click VMware vCenter Multi-Hypervisor Manager, and select Enable.

    This issue is resolved in this release.

  • The vSphere Client might report an error while adding a Hyper-V host
    In the Add Host wizard, when you click Next in the Connection Settings page to proceed to the Host Summary page, one of the following errors might appear:
    An error occurred while trying to connect to the third-party host.
    Could not add host <host_name> to the TrustedHosts list of the Windows Remote Management (WinRM) client configuration. Add the host manually.

    or
    An error occurred while trying to connect to the third-party host.
    Call "XhmServiceInstance.QueryConnectionInfo" for object "XhmServiceInstance" on Server <IP address> failed.

    This issue is resolved in this release.

  • Top of Page

    Known Issues

    The known issues in this vCenter Multi-Hypervisor Manager release are grouped as follows:


    Installing vCenter Multi-Hypervisor Manager

    • Installation of vCenter Multi-Hypervisor Manager fails with an error on Windows Server 2003 if you open two installer wizards
      If you start two installer wizards for vCenter Multi-Hypervisor Manager by quickly clicking too many times on the installation executable file, both installation instances fail with the following error:
      Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action InstallVCRedistributable, location ...\vcredist_x64...
      Workaround: Click Finish on both messages, and attempt to install vCenter Multi-Hypervisor Manager again by opening only one installer wizard.
    • Installation of vCenter Multi-Hypervisor Manager fails with an error
      While installing vCenter Multi-Hypervisor Manager, if you choose to provide a custom certificate for vCenter Multi-Hypervisor Manager, and provide an IPv6 address in any of the following places, the installation fails with an error:
      • The IP address or host name field of the vCenter Server page
      • The IP address or host name field of the vCenter Converter Standalone page
      The error message that is displayed is:
      Failed to verify the vCenter Server certificate.
      Workaround: In the text box for the IP address or host name, type the host name or IPv4 address for the vCenter Server.
    • You cannot use credentials that contain an ampersand (&) character to authenticate with your vCenter Server system
      On the vCenter Server page of the installer wizard, when you type authentication credentials that contain an ampersand (&) character and click Next, the following error message appears:
      General error.
      Workaround: Provide authentication credentials that do not contain an ampersand (&) character.
    • You cannot use the semicolon (;) character in text boxes of the installer wizard
      When you provide a string that contains a semicolon (;) and click Next, an error message similar to the following appears and the installation cannot proceed.
      Invalid parameter error <property>.
      The <property> varies depending on the text box in which you have typed a semicolon (;).
      Workaround: When you install and configure vCenter Multi-Hypervisor Manager, do not provide authentication credentials, file paths, or host names that contain a semicolon (;).
    • Attempt to install vCenter Multi-Hypervisor Manager server fails when the Windows Services window is open
      Attempts to install vCenter Multi-Hypervisor Manager server fail if a Windows Services window is open. The following error message is displayed:
      Error 1923.Service VMware Multi-Hypervisor Manager (MHM) could not be installed. Verify that you have sufficient privileges to install system services.
      Workaround: Close the Windows Services window and attempt installing vCenter Multi-Hypervisor Manager server again.


    Using vCenter Multi-Hypervisor Manager

    • The task to generate log bundle does not complete on Windows Server 2003 systems
      On Windows Server 2003, while collecting log files, the script for vCenter Multi-Hypervisor Manager log bundle stops and the process of generating the log .zip file is interrupted.
      Workaround: Press Enter on your keyboard twice to proceed generating the log bundle. You have to press Enter twice on your keyboard each time the script stops generating the log bundle. When the log .zip file is successfully saved to your system, confirmation appears on your screen.
    • Two hosts in the inventory of vCenter Multi-Hypervisor Manager have identical virtual machines and configuration, and synchronize simultaneously
      You can add one and the same Hyper-V host twice in the inventory of vCenter Multi-Hypervisor Manager if the host uses different network names or IP addresses. This is possible if the Hyper-V host has more than one network interface. Adding the same Hyper-V host twice does not cause any problems for the vCenter Server Multi-Hypervisor Manager server.
      Workaround: Remove one of the instances of the Hyper-V host from the inventory of vCenter Server Multi-Hypervisor Manager.
    • When an attempt to create a virtual machine fails, unnecessary virtual hard disk files might be created
      When you create a virtual machine with a new hard disk and the operation fails, the .vhd files for the new virtual hard disk are still created. For example, if you select an invalid CD or DVD-ROM in the last window of the Create Virtual Machine wizard, the create new virtual machine operation fails but the virtual hard disk files (.vhd) are created.
      Workaround: Navigate to the location of the corresponding data store on the Hyper-V server and delete the unnecessary .vhd files.
    • The state of a Hyper-V host might not be refreshed in the vSphere Client
      If you shut down the Hyper-V host independently from vCenter Multi-Hypervisor Manager, the state of the Hyper-V host is not refreshed in the vSphere Client. For example, when you shut down the Hyper-V host through its operating system, its state is not refreshed in the vSphere Client.
      Workaround: Restart the vCenter Multi-Hypervisor Manager plug-in. To restart the vCenter Multi-Hypervisor Manager plug-in, perform the following steps:
      1. In the vSphere Client, click Plug-ins and select Manage Plug-ins.
      2. Right-click VMware vCenter Multi-Hypervisor Manager, and select Disable.
      3. Right-click VMware vCenter Multi-Hypervisor Manager, and select Enable.
    • The vCenter Multi-Hypervisor Manager server is unable to connect to a Hyper-V host
      If the TrustedHosts list of the Windows Remote Management (WinRM) client configuration on the system where vCenter Multi-Hypervisor Manager server runs contains more than 1023 characters, you cannot add Hyper-V hosts to the third-party hosts inventory in vCenter Server.
      Workaround: Perform a clean up to the TrustedHosts list of the WinRM client configuration. To perform a clean up to the TrustedHosts list of the WinRM client configuration, open a command-line window on the system where the vCenter Multi-Hypervisor Manager server is installed, and run a command that sets the list.
      For example, run the following command:

      winrm set winrm/config/client @{TrustedHosts="<NEW VALUE>"}

      Here <NEW VALUE> is the hostname or the IP address of the host you want to add to the TrustedHosts list of the WinRM client configuration. If you want to trust any host, type <*>.

    Top of Page