What were you trying to do that didn't work?

A Windows 2025 virtual machine was successfully migrated from a VMware environment to a local libvirt RHEL host. Upon first boot in the new environment, the VM fails to load the operating system and becomes stuck in the "Preparing Automatic Repair" loop.

What is the impact of this issue to you?

After a successful virt-v2v migration, the post-migration checkpoint validation fails or cannot be executed, preventing verification of the migrated VM's integrity.

Please provide the package NVR for which the bug is seen:

qemu-img-7.2.0-14.el9_2.21.x86_64
libguestfs-1.48.4-4.el9.x86_64
virt-v2v-2.2.0-7.el9_2.x86_64
virtio-win-1.9.34-0.el9_2.noarch

How reproducible is this bug?:

100%

Steps to reproduce:

1. Create Windows2025 VM on VMWare esxi environment
2. Convert/Migrate VM using virt-v2v
3. Boot the VM using virsh start command and check installation process in GUI

Expected results:

Post migration, VM should boot successfully and all the v2v checkpoints should be passed

Actual results:

VM does not boot successfully.

PFA: Screenshot and v2v conversion logs attached