Right now MTV does not support migrating from HyperV. Users need to export images from HyperV node and import it via some other means such as OVA. However HyperV supports disks to be stored on SMB so we could create provider similar to OVA which would directly get HyperV disks from SMB.

The challenge being addressed is that MTV does not currently include a provider for Hyper-V, forcing users to perform manual steps: export the VM disk images (VHD/VHDX) from the Hyper-V node and then import them via a different mechanism, such as using an Open Virtual Appliance (OVA) provider.

The goal of MTV-3635 is to bypass these manual steps by:

• Leveraging SMB Storage: Since Hyper-V supports storing VM disks on SMB (Server Message Block) shares, MTV can potentially read the disks directly from this network location.

• Creating a New Provider: The ticket proposes developing a new provider, similar to the existing OVA provider, that would directly access and ingest the Hyper-V disk images from the SMB share.

The key benefit is streamlining the migration process for Hyper-V VMs by automating the disk transfer and eliminating the current requirement for manual export and subsequent OVA import.

MTV-3635 Description

JTBD statement

When I am migrating virtual machines from a Microsoft Hyper-V environment that stores disks on SMB, I want to configure the Migration Toolkit for Virtualization (MTV) to automatically access and transfer the Hyper-V disks directly via the SMB share, so I can eliminate the time-consuming and manual process of exporting, packaging (e.g., as OVA), and re-importing those virtual machine images.

Personas

• As a Migration Engineer i want to utilize a dedicated Hyper-V provider in MTV that accesses disks over SMB to achieve full automation of the disk transfer and migration process, eliminating the manual, error-prone export and OVA conversion steps.

• As a Systems Owner i want to move my critical Hyper-V virtual machines (such as domain controllers or application servers) to achieve a seamless, reliable migration to Red Hat OpenShift Virtualization with minimal downtime and assured data integrity.

• As a Virtualization Administrator i want to leverage the existing SMB storage setup of my Hyper-V environment directly in the migration tool to achieve simplification of the integration between my source and destination platforms, reducing networking complexity and the number of manual steps required.

• As a Cloud Architect i want to consolidate my diverse virtual machine environments, including Hyper-V, onto the Red Hat OpenShift platform to achieve standardized infrastructure management on a single stack, increasing operational efficiency and reducing vendor lock-in.