-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.5
-
None
-
virt-v2v-2.5.4-1.el9
-
None
-
Moderate
-
rhel-sst-virtualization
-
ssg_virtualization
-
12
-
16
-
2
-
False
-
-
None
-
None
-
Pass
-
Manual
-
None
Description of problem:
Virt-v2v can't convert guest from maintained ESXi hosts with vddk > 6
Version-Release number of selected component (if applicable):
virt-v2v-2.5.2-1.el9.x86_64
libguestfs-1.50.1-7.el9.x86_64
nbdkit-1.36.2-1.el9.x86_64
libnbd-1.18.1-3.el9.x86_64
libvirt-libs-10.0.0-6.2.el9_4.x86_64
qemu-img-8.2.0-11.el9_4.1.x86_64
How reproducible:
100%
Steps:
1. Turn ESXi host into in maintenance mode on vsphere client
2. Can dump guest libvirt xml from maintained ESX8.0.1i host by virsh
# virsh -c vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?no_verify=1 dumpxml esx8.0-win11-x86_64-uefi-vtpm Enter administrator@vsphere.local's password for 10.73.212.129: <domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'> <name>esx8.0-win11-x86_64-uefi-vtpm</name> <uuid>4220a166-b294-5d2b-d70c-34386e02f154</uuid> <genid>10e431a4-e8b5-98ee-3d35-41db3d40fc9e</genid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static'>2</vcpu> <cputune> <shares>2000</shares> </cputune> <os firmware='efi'> <type arch='x86_64'>hvm</type> </os> ......
3. Convert a guest from maintained ESXi hosts without vddk by virt-v2v
# virt-v2v -ic vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?no_verify=1 -ip /home/passwd esx8.0-win11-x86_64-uefi-vtpm -o null [ 0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?no_verify=1 esx8.0-win11-x86_64-uefi-vtpm [ 2.4] Opening the source [ 42.6] Inspecting the source [ 674.6] Checking for sufficient free disk space in the guest [ 674.6] Converting Windows 10 Enterprise to run on KVM virt-v2v: This guest has virtio drivers installed. [ 864.1] Mapping filesystem data to avoid copying unused and blank areas [1508.8] Closing the overlay [1509.1] Assigning disks to buses [1509.1] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [1509.1] Setting up the destination: -o null [1510.5] Copying disk 1/1 ^Cvirt-v2v: Exiting on signal SIGINT------------]
4. Convert a guest from maintained ESXi hosts with vddk6.7 by virt-v2v
# virt-v2v -ic vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk6.7 -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-win11-x86_64-uefi-vtpm -o null [ 0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?no_verify=1 -it vddk esx8.0-win11-x86_64-uefi-vtpm [ 1.8] Opening the source [ 8.0] Inspecting the source [ 13.6] Checking for sufficient free disk space in the guest [ 13.6] Converting Windows 10 Enterprise to run on KVM virt-v2v: This guest has virtio drivers installed. [ 21.6] Mapping filesystem data to avoid copying unused and blank areas [ 24.5] Closing the overlay [ 24.8] Assigning disks to buses [ 24.8] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 24.8] Setting up the destination: -o null [ 26.3] Copying disk 1/1 █ 100% [****************************************] [ 230.3] Creating output metadata [ 230.3] Finishing off
5. Convert a guest from maintained ESXi hosts with vddk7.0.3 by virt-v2v
# virt-v2v -ic vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.3 -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-win11-x86_64-uefi-vtpm -o null [ 0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?no_verify=1 -it vddk esx8.0-win11-x86_64-uefi-vtpm [ 1.9] Opening the source nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available virt-v2v: error: libguestfs error: could not create appliance through libvirt. Try running qemu directly without libvirt using this environment variable: export LIBGUESTFS_BACKEND=direct Original error from libvirt: internal error: process exited while connecting to monitor: 2024-04-23T03:15:27.806294Z qemu-kvm: -blockdev {"driver":"nbd","server":\{"type":"unix","path":"/tmp/v2v.YnjPQb/in0"},"node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap","cache":\{"direct":false,"no-flush":true}}: Requested export not available [code=1 int1=-1] If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...]
6. Convert a guest from maintained ESXi hosts with vddk8.0.2 by virt-v2v
# virt-v2v -ic vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?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-win11-x86_64-uefi-vtpm -o null [ 0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local@10.73.212.129/data/10.73.225.34/?no_verify=1 -it vddk esx8.0-win11-x86_64-uefi-vtpm [ 1.8] Opening the source nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore1 (3)] esx8.0-win11-x86_64-uefi-vtpm/esx8.0-win11-x86_64-uefi-vtpm.vmdk: The host is not available virt-v2v: error: libguestfs error: could not create appliance through libvirt. Try running qemu directly without libvirt using this environment variable: export LIBGUESTFS_BACKEND=direct Original error from libvirt: internal error: process exited while connecting to monitor: 2024-04-22T16:05:20.136737Z qemu-kvm: -blockdev {"driver":"nbd","server":\{"type":"unix","path":"/tmp/v2v.v0z86d/in0"},"node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap","cache":\{"direct":false,"no-flush":true}}: Requested export not available [code=1 int1=-1] If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...]
- links to
-
RHBA-2024:129426 virt-v2v bug fix and enhancement update