Blocker Description of problem：
The libguestfs appliance sometimes crashes when do v2v conversions on a fresh RHEL 10.2 server.
Version-Release number of selected component (if applicable):
virt-v2v-2.9.9-4.el10.x86_64
libguestfs-1.57.5-1.el10.x86_64
guestfs-tools-1.54.0-6.el10.x86_64
How reproducible:
20%
Steps:
1.Prepare a newly installed rhel10.2 server and convert a windows guest from VMware by virt-v2v
# virt-v2v -ic vpx://non-admin%40vsphere.local@10.73.213.134/data/cluster/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk9.0.0 -io vddk-thumbprint=C3:83:1D:C0:6D:4C:47:83:5A:B9:6E:0E:FA:5A:15:22:B4:75:D5:7E -ip /home/passwd esx8.0-win2016-bug-RHEL-124569-with-name-TEMP -o local -os /home [ 0.0] Setting up the source: -i libvirt -ic vpx://non-admin%40vsphere.local@10.73.213.134/data/cluster/10.73.212.36/?no_verify=1 -it vddk esx8.0-win2016-bug-RHEL-124569-with-name-TEMP [ 1.9] Opening the source [ 74.2] Checking filesystem integrity before conversion [ 76.3] Detecting if this guest uses BIOS or UEFI to boot [ 78.4] Inspecting the source [ 90.7] Detecting the boot device [ 90.7] Checking for sufficient free disk space in the guest [ 90.7] Converting Windows Server 2016 Standard (win2k16) to run on KVM virt-v2v: error: /usr/share/virtio-win/virtio-win.iso: cannot open virtio-win ISO file: guestfs_launch failed. This usually means the libguestfs appliance failed to start or crashed. Do: export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 and run the command again. For further information, read: http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs You can also run 'libguestfs-test-tool' and post the *complete* output into a bug report or message to the libguestfs mailing list. If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] # rpm -q virtio-win virtio-win-1.9.48-0.el10.noarch
2. Convert the guest by v2v again, the conversion can finish without error
# virt-v2v -ic vpx://non-admin%40vsphere.local@10.73.213.134/data/cluster/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk9.0.0 -io vddk-thumbprint=C3:83:1D:C0:6D:4C:47:83:5A:B9:6E:0E:FA:5A:15:22:B4:75:D5:7E -ip /home/passwd esx8.0-win2016-bug-RHEL-124569-with-name-TEMP -o local -os /home [ 0.0] Setting up the source: -i libvirt -ic vpx://non-admin%40vsphere.local@10.73.213.134/data/cluster/10.73.212.36/?no_verify=1 -it vddk esx8.0-win2016-bug-RHEL-124569-with-name-TEMP [ 1.8] Opening the source [ 70.3] Checking filesystem integrity before conversion [ 72.5] Detecting if this guest uses BIOS or UEFI to boot [ 74.6] Inspecting the source [ 86.6] Detecting the boot device [ 86.7] Checking for sufficient free disk space in the guest [ 86.7] Converting Windows Server 2016 Standard (win2k16) to run on KVM ** (process:63001): WARNING **: 04:30:10.193: Entity http://pcisig.com/pci/1af4/1012 referenced but not defined virt-v2v: This guest has virtio drivers installed. [ 120.4] Setting a random seed virt-v2v: warning: random seed could not be set for this type of guest [ 120.4] SELinux relabelling [ 120.6] Fixing NTFS permissions [ 120.7] Mapping filesystem data to avoid copying unused and blank areas [ 126.3] Checking filesystem integrity after conversion [ 128.4] Closing the overlay [ 128.8] Assigning disks to buses [ 128.8] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 128.8] Setting up the destination: -o disk -os /home [ 133.8] Copying disk 1/9 █ 100% [****************************************] [ 412.8] Copying disk 2/9 █ 100% [****************************************] [ 413.6] Copying disk 3/9 █ 100% [****************************************] [ 414.3] Copying disk 4/9 █ 100% [****************************************] [ 414.9] Copying disk 5/9 █ 100% [****************************************] [ 415.4] Copying disk 6/9 █ 100% [****************************************] [ 416.0] Copying disk 7/9 █ 100% [****************************************] [ 416.6] Copying disk 8/9 █ 100% [****************************************] [ 417.5] Copying disk 9/9 █ 100% [****************************************] [ 418.3] Creating output metadata [ 418.3] Finishing off
Actual result:
As above description
Expect result:
Fix the bug
Additional info
The same issue was encountered during testing bug RHEL-111165. Please see the comment posted on October 10, 2025 at 9:15 AM.
