Skip to main content
NetApp virtualization solutions

Convert VMs using the Shift Toolkit

Contributors netapp-jsnyder kevin-hoke
PDFs

Use the Shift Toolkit to convert VMware ESX virtual machine disks (VMDK) to Microsoft Hyper-V (VHDX) disk format or Red Hat KVM (QCOW2) disk format. This process includes setting up resource groups, creating conversion blueprints, and scheduling conversions.

Conversion

The Clone based conversion option allows to simply convert the virtual disk between hypervisors for the following disk formats:

  • VMware ESX to Microsoft Hyper-V (VMDK to VHDX)

  • VMware ESX to Red Hat KVM (VMDK to QCOW2)

The converted qcow2 files are compatible with any KVM hypervisors. For example, a qcow2 file can be utilized with RHEL-based KVM using virt-manager to create a VM, as well as with ubuntu KVM, Rocky Linux based KVM and others. The same can be used with Oracle Linux virtualization manager with a tweak and with OpenShift virtualization after importing using NetApp Trident. The goal is to provide the disk (converted in secs to mins) which can then be integrated into existing automation scripts used by organizations to provision the VM and assign the network. This approach helps reduce overall migration times, with disk conversion handled by Shift toolkit APIs and the remaining script bringing up the VMs.

In future releases, Shift toolkit will support end-to-end migration from VMware to other compatible KVM hypervisors. However, with the current release, the conversion can be performed via the UI or APIs.

Convert to QCOW2 format

To convert the virtual disks to QCOW2 format with NetApp Shift toolkit, follow these high-level steps:

  • Create a destination site type specifying KVM as the hypervisor.

    Note Hypervisor details are not required for KVM.

    Figure showing input/output dialog or representing written content

  • Create a resource group with the VMs for which the disk conversion is required

    Figure showing input/output dialog or representing written content

    Figure showing input/output dialog or representing written content

    Figure showing input/output dialog or representing written content

  • Create the blueprint to convert the virtual disk to QCOW2 format.

    Figure showing input/output dialog or representing written content

    Figure showing input/output dialog or representing written content

    Figure showing input/output dialog or representing written content

  • Designate a slot using the scheduling option. If the conversion is to be performed on an ad-hoc basis, leave the scheduling option unchecked.

    Figure showing input/output dialog or representing written content

  • Once the blueprint is created, a prepareVM job is initiated and it automatically runs scripts on the source VMs to prepare them for conversion.

    Figure showing input/output dialog or representing written content

  • Once the prepareVM job completes successfully (as shown in the screenshot below), the VM disks associated with the VMs are ready for conversion, and the blueprint status will update to "Active."

  • Click "Convert" after scheduling the required downtime for the VMs.

    Figure showing input/output dialog or representing written content

  • The convert operation uses a point-in-time snapshot. Power off the VM if needed and then retrigger the operation.

    Figure showing input/output dialog or representing written content

    • The convert operation executes each operation against the VM and respective disk to generate the appropriate format.

      Figure showing input/output dialog or representing written content

  • Use the converted disk by manually creating the VM and attaching the disk to it.

    Figure showing input/output dialog or representing written content

Note The Shift toolkit supports disk conversions only for the qcow2 format. It doesn't support VM creation or registration. To use the converted disk, manually create the VM and attach the disk.

Convert to VHDX format

To convert the virtual disks to VHDX format with NetApp Shift toolkit, follow these high-level steps:

  • Create a destination site type specifying Hyper-V as the hypervisor.

  • Create a resource group with the VMs for which the disk conversion is required

    Figure showing input/output dialog or representing written content

    Figure showing input/output dialog or representing written content

  • Create the blueprint to convert the virtual disk to VHDX format. Once the blueprint is created, the preparation jobs will be automatically initiated.

    Figure showing input/output dialog or representing written content

  • Choose "Convert" once the required downtime for the VMs has been scheduled.

    Figure showing input/output dialog or representing written content

  • The convert operation executes each operation against the VM and respective disk to generate the appropriate VHDX format.

    Figure showing input/output dialog or representing written content

  • Use the converted disk by manually creating the VM and attaching the disk to it.

    Figure showing input/output dialog or representing written content

Note To use the converted VHDX disk in a VM, the VM must be created manually via Hyper-V manager or PowerShell commands, and the disk must be attached to it. Along with this, network should also be mapped manually.