> Documentation > Backup and Restore Agents > Virtualization > Virtual Server Agent > Cross-Hypervisor Restores (Virtual Machine Conversion) > Converting from VMware 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. You need to 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.

Loading...