Converting VMware Virtual Machines to Microsoft Hyper-V

When restoring a VMware full virtual machine, you can restore as Microsoft Hyper-V to create a new Hyper-V virtual machine from the last successful full backup. This option enables you to duplicate a VMware virtual machine for the Hyper-V environment, or to migrate a VM from VMware to Hyper-V.

To get the most up-to-date instance of a virtual machine, power off the source VM and perform a backup before initiating the conversion.

Before You Begin

  • At least one Hyper-V node must be configured on the CommServe host; otherwise the Restore as option for Hyper-V is not displayed.
  • The destination client must be a Hyper-V server that has the Virtual Server Agent installed.


Perform the following steps to access a VMware backup and create a Hyper-V virtual machine:

  1. From the CommCell Console, navigate to Client Computers > virtualization_client > Virtual Server > VMware > backup_set.
  2. Right-click the subclient that contains the backup for the VMware virtual machine to convert and then select Browse and Restore.
  3. In the Browse and Restore Options window, select Full Virtual Machine.
  4. From the Restore as list under Full Virtual Machine, select Microsoft Hyper-V.
  5. Click View Content.

    A Client tab shows the contents of the most recent backup for the subclient.

  6. Select a virtual machine in the left pane.

    The configuration and VMDK files for the selected virtual machine are displayed in the right pane.

  7. Click Recover All Selected at the bottom of the window.
  8. On the Restore Options for All Selected Items dialog, select values for the conversion:
    Option Steps
    Select a destination client: The destination client must be Hyper-V server that is running Windows Server 2012 R2 and has the Virtual Server Agent installed.
    • Select a Hyper-V server from the Destination Client list.

      The new Hyper-V virtual machine is automatically mounted to the Hyper-V server you select.

    Restore location: Select one of the following options:
    • New folder

      Select a location for the VM on the destination client:

      1. Click in the first row of the Destination Path column and click the browse button (...).
      2. Select a folder on the destination client where you want to restore the virtual machine and click OK.

      The destination path can be the path of a cluster shared volume (CSV).

      All virtual machine disks are restored to this path unless you specify different paths for each disk.

    • Hyper V default folder

      Create the virtual machine on the default location of the Hyper-V server when you do not know which volume on the server has the space required to restore the virtual machine.

    VM and Disk: The VM and Disk column displays the name of the virtual machine and lists the virtual machine disks.
    Change the VM display name: To avoid overwriting an existing virtual machine with the same name on the Hyper-V server:
    •  Click in the first row of  the Change VM display name to column and enter a new name.
    Destination Path: To restore each virtual machine disk in a different location:
    • Click each row in the Destination Path column and select a location for the corresponding disk.
    Automatically power on restored virtual machines: To power on the virtual machine automatically after the restore operation completes:
    • Select Power On Virtual Machine after restore.
    Overwrite an existing VM: If a virtual machine with the same name exists on the destination, select the Unconditionally overwrite VM and VHDs in destination path check box to overwrite the existing virtual machine.
    Register Virtual Machine with Failover Cluster:

    Select Register Virtual Machine with Failover Cluster to register the virtual machine with the failover cluster immediately after the restore. Once the virtual machine is registered, you can migrate it to any Hyper-V server in the cluster.


    • To register the Virtual Machine with the failover cluster, the user name entered when creating the virtualization client must be part of the Hyper-V Administrators group.
    • For a Hyper-V cluster, the user account must have full Cluster Permissions (Read and Full Control).

    When the virtual machine is created, it is automatically registered with the failover cluster.

    Note: If UAC (User Account Control) is enabled on a virtual machine running on 2008 R2 Hyper-V server, you must register the VM with the failover cluster manually.

  9. Click OK.
  10. To ensure that the converted VM is fully functional, continue with Updating a Virtual Machine Converted to Hyper-V.

Updating a Virtual Machine Converted to Hyper-V

The conversion from VMware to Hyper-V only moves the virtual machine data and configuration to the Hyper-V format, and does not change any settings inside the virtual machine. As a result, you may need to update the converted virtual machine for the Hyper-V environment. This is especially true for virtual machines with older operating systems.

After conversion, you may need to perform the following additional tasks:

  • For virtual machines running Windows versions earlier than Windows 2008 R2, install the latest version of Hyper-V integration services tools on the virtual machine.
  • If the source virtual machine used IDE 0:0 for a non-OS disk, you might not be able to boot the converted virtual machine.  This issue can occur on a virtual machine with a legacy operating system, such as Windows 2003 with SP1, that does not have the IDE driver loaded. If you are still unable to boot the converted VM, repair the virtual machine using the operating system disk.
  • If a non-OS disk that was attached to SCSI controllers in the source VM is offline after conversion, bring the disk online manually using disk management.
  • If the source VM had dynamic disks that use simple disk spanning, RAID, striped, or mirrored layouts, after VM conversion, the disks in the converted VM might be marked as Failed in Disk Management. You must bring these disks online manually using Disk Management. To bring the disks back online, perform an Import Foreign Disks operation on the guest VM for the disk group that contains failed disks. As noted in Description of Disk Groups in Windows Disk Management, import the entire disk group in one operation rather than performing a partial import.

  • Network connections are not configured automatically. If the virtual machine has more than one network adapter and none of the adapters can match the source network name, you must manually configure the network adapter after conversion.
  • After converting a RHEL 7.2 virtual machine from VMware to Hyper-V, the VM will not boot because the SCSI boot disk is replaced by an IDE boot disk, and the default optimized initial RAM file system for RHEL 7.2 does not include the required driver for the IDE root disk. Perform the following steps to resolve this issue:
    1. Boot the converted VM using the Rescue Mode option.

      The initial RAM file system for Rescue Mode includes the IDE driver.

    2. Make a backup of the initial RAM disk (initrd).
    3. Run the following command to generate a new initial RAM file system for the converted VM:

      dracut -f

      This command loads IDE modules that are needed to access the root file system.

    4. Reboot the virtual machine using the default boot option.
  • After converting a UNIX VM:
    • Xserver might not be configured correctly. You can set up Xserver manually after conversion.
    • Starting the VM fails with the error Kernel Panic - not syncing: IO-APIC + timer doesn't work! Boot with “noapic” option. To resolve this issue, pass the no_timer_check argument to the kernel command line at the boot prompt.
    • For operating systems such as SUSE Linux 11.2 or Ubuntu 10.4, the eth0 setting is preserved but the network interface card (NIC) may not be operational. To enable network connections:
      • For SUSE Linux:
        1. Start YaST and remove the existing NIC device.
        2. Add a legacy network adapter.
        3. Use YaST to configure a new network card.

        Note: When you install a new Suse Linux operating system, on a Hyper-V machine. you can use a regular network adapter, detected as "Virtual Ethernet controller." After converting a VMware VM, the legacy NIC is detected as "DECchip 21140."

      • For Ubuntu 10.4:
        1. Run the ip addr command to find the network adapter.
        2. Edit the /etc/network/interfaces to add a legacy NIC and IDE disks.