# virt-v2v -ic vpx://root@10.73.212.129/data/10.73.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk8.0.2 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43 -ip /home/passwd   esx8.0-win2022-x86_64-efi  
[   0.0] Opening the source -i libvirt -ic vpx://root@10.73.212.129/data/10.73.212.36/?no_verify=1 esx8.0-win2022-x86_64-efi -it vddk  -io vddk-libdir=/home/vddk8.0.2 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43
nbdkit: error: libssl.so.3: cannot open shared object file: No such file or directory

If 'lib64/libvixDiskLib.so.8' is located on a non-standard path you may need to
set libdir=/path/to/vmware-vix-disklib-distrib.

See nbdkit-vddk-plugin(1) man page section "LIBRARY LOCATION" for details.

virt-v2v: error: nbdkit did not start up.  There may be errors printed by 
nbdkit above.

If the messages above are not sufficient to diagnose the problem then add 
the ‘virt-v2v -v -x’ options and examine the debugging output 
carefully.

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]

# virt-v2v -ic vpx://root@10.73.212.129/data/10.73.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk8.0.1 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43 -ip /home/passwd   esx8.0-win2022-x86_64-efi  
[   0.0] Opening the source -i libvirt -ic vpx://root@10.73.212.129/data/10.73.212.36/?no_verify=1 esx8.0-win2022-x86_64-efi -it vddk  -io vddk-libdir=/home/vddk8.0.1 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43
[   1.8] Creating an overlay to protect the source from being modified
nbdkit: vddk[1]: error: VDDK_PhoneHome: Unable to load configuration options from /tmp/vmware-root/vacConfig.conf.
[   3.0] Opening the overlay
[  17.0] Inspecting the overlay
[  22.2] Checking for sufficient free disk space in the guest
[  22.2] Estimating space required on target for each disk
[  22.2] Converting Windows Server 2022 Standard to run on KVM
virt-v2v: This guest has virtio drivers installed.
[  35.1] Mapping filesystem data to avoid copying unused and blank areas
virt-v2v: warning: fstrim on guest filesystem /dev/sda1 failed.  Usually 
you can ignore this message.  To find out more read "Trimming" in 
virt-v2v(1).

Original message: fstrim: fstrim: /sysroot/: the discard operation is not 
supported
[  35.9] Closing the overlay
[  36.2] Assigning disks to buses
[  36.2] Checking if the guest needs BIOS or UEFI to boot
virt-v2v: This guest requires UEFI on the target to boot.
[  36.2] Initializing the target -o libvirt -os default
[  36.2] Copying disk 1/1 to /var/lib/libvirt/images/esx8.0-win2022-x86_64-efi-sda (raw)
    (100.00/100%)
[ 258.4] Creating output metadata
[ 258.5] Finishing off

# rpm -q virt-v2v libguestfs nbdkit
virt-v2v-2.4.0-2.el9.x86_64
libguestfs-1.50.1-7.el9.x86_64
nbdkit-1.36.2-1.el9.x86_64

# virt-v2v -ic vpx://root@10.73.212.129/data/10.73.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk8.0.2 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43 -ip /home/passwd   esx8.0-win2022-x86_64-efi  -o null
[   0.1] Setting up the source: -i libvirt -ic vpx://root@10.73.212.129/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-win2022-x86_64-efi
[   2.3] Opening the source
[   9.5] Inspecting the source
[  15.9] Checking for sufficient free disk space in the guest
[  15.9] Converting Windows Server 2022 Standard to run on KVM
virt-v2v: This guest has virtio drivers installed.
[  31.9] Mapping filesystem data to avoid copying unused and blank areas
[  33.6] Closing the overlay
[  33.9] Assigning disks to buses
[  33.9] Checking if the guest needs BIOS or UEFI to boot
virt-v2v: This guest requires UEFI on the target to boot.
[  33.9] Setting up the destination: -o null
[  35.6] Copying disk 1/1
█ 100% [****************************************]
[ 338.8] Creating output metadata
[ 338.8] Finishing off