This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2188613 - Virt-v2v can't convert guest with disk mode 'independent' from VMware via vddk >= 7.0
Summary: Virt-v2v can't convert guest with disk mode 'independent' from VMware via vdd...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-v2v
Version: 9.3
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-21 11:51 UTC by mxie@redhat.com
Modified: 2023-07-10 11:22 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-10 11:22:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)
vmware-guest-with-independent-disk-mode.png (79.47 KB, image/png)
2023-04-21 11:51 UTC, mxie@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-758 0 None None None 2023-07-10 11:22:27 UTC
Red Hat Issue Tracker RHELPLAN-155397 0 None None None 2023-04-21 11:52:55 UTC

Description mxie@redhat.com 2023-04-21 11:51:28 UTC
Created attachment 1958796 [details]
vmware-guest-with-independent-disk-mode.png

Description of problem:
Virt-v2v can't convert guest with disk mode 'independent' from VMware via vddk >= 7.0
 
Version-Release number of selected component (if applicable):
virt-v2v-2.3.4-1.el9.x86_64
libguestfs-1.50.1-3.el9.x86_64
guestfs-tools-1.50.1-2.el9.x86_64
nbdkit-server-1.34.0-1.el9.x86_64
libnbd-1.16.0-1.el9.x86_64
libvirt-libs-9.2.0-1.el9.x86_64
qemu-img-7.2.0-14.el9_2.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Prepare a guest which has disk mode 'indepentent' on VMware, pls refer to scrreenshot 'vmware-guest-with-independent-disk-mode.png'

2. Convert the guest from VMware via vddk>=7.0 by virt-v2v
2.1 with vddk8.0.0
# virt-v2v -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94 -ip /home/passwd  esx8.0-rhel9.3-x86_64
[   0.0] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-rhel9.3-x86_64
[   1.9] Opening the source
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
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: 2023-04-21T10:07:03.922622Z qemu-kvm: -blockdev 
{"driver":"nbd","server":{"type":"unix","path":"/tmp/v2v.zxZ5Sg/in0"},"node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":true},"auto-read-only":true,"discard":"unmap"}: 
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 [...]

2.2  with vddk7.0
# virt-v2v -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk7.0 -io vddk-thumbprint=D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94 -ip /home/passwd  esx8.0-rhel9.3-x86_64
[   0.0] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-rhel9.3-x86_64
[   1.9] Opening the source
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
nbdkit: vddk[1]: error: VixDiskLib_Open: [esx8.0-matrix] esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94) matches the SHA1 fingerprint of the remote VMware server.  Refer to nbdkit-vddk-plugin(1) section "THUMBPRINTS" for details.
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: 2023-04-21T11:36:37.840542Z qemu-kvm: -blockdev 
{"driver":"nbd","server":{"type":"unix","path":"/tmp/v2v.WwjOCy/in0"},"node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":true},"auto-read-only":true,"discard":"unmap"}: 
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 [...]


Actual results:
As above description

Expected results:
Maybe the bug is caused by vddk library, v2v can improve the error or something

Additional info:
1. Can Convert the guest from VMware via vddk<7.0 by virt-v2v
1.1 # virt-v2v -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk6.7 -io vddk-thumbprint=D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94 -ip /home/passwd  esx8.0-rhel9.3-x86_64
[   0.0] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-rhel9.3-x86_64
[   1.8] Opening the source
[  10.1] Inspecting the source
[  22.7] Checking for sufficient free disk space in the guest
[  22.7] Converting Red Hat Enterprise Linux 9.3 Beta (Plow) to run on KVM
^Cvirt-v2v: Exiting on signal SIGINT

1.2 # virt-v2v -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk6.5 -io vddk-thumbprint=D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94 -ip /home/passwd  esx8.0-rhel9.3-x86_64
[   0.9] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-rhel9.3-x86_64
[   2.7] Opening the source
[  13.9] Inspecting the source
[  26.6] Checking for sufficient free disk space in the guest
[  26.6] Converting Red Hat Enterprise Linux 9.3 Beta (Plow) to run on KVM
^Cvirt-v2v: Exiting on signal SIGINT

2. Can convert the guest from VMware without vddk by virt-v2v
# virt-v2v -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1  -ip /home/passwd  esx8.0-rhel9.3-x86_64[   0.0] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 esx8.0-rhel9.3-x86_64
[   2.5] Opening the source
[  37.5] Inspecting the source
[ 795.6] Checking for sufficient free disk space in the guest
[ 795.6] Converting Red Hat Enterprise Linux 9.3 Beta (Plow) to run on KVM
^Cvirt-v2v: Exiting on signal SIGINT

3. Can convert the guest from VMware via vmx+ssh by virt-v2v
# virt-v2v -i vmx -it ssh ssh://root.212.36/vmfs/volumes/esx8.0-matrix/esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmx -ip /home/esxpwd
[   0.0] Setting up the source: -i vmx ssh://root.212.36/vmfs/volumes/esx8.0-matrix/esx8.0-rhel9.3-x86_64_1/esx8.0-rhel9.3-x86_64.vmx
The authenticity of host '10.73.212.36 (10.73.212.36)' can't be established.
ECDSA key fingerprint is SHA256:kV9S4wQ7Amf6K+Gfkl8MeLKsPZ2OyS/3dfQq0TEMONc.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
(root.212.36) Password: 
(root.212.36) Password: 
(root.212.36) Password: 
(root.212.36) Password: 
[  41.1] Opening the source
[  46.4] Inspecting the source
[  57.5] Checking for sufficient free disk space in the guest
[  57.5] Converting Red Hat Enterprise Linux 9.3 Beta (Plow) to run on KVM
^Cvirt-v2v: Exiting on signal SIGINT

Comment 6 Richard W.M. Jones 2023-05-05 11:55:09 UTC
Moving to the backlog as I don't really know what to do with this bug,
but I don't want to keep getting emails about it.


Note You need to log in before you can comment on or make changes to this bug.