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 2147528 - [RFE]Virt-v2v supports converting guest with RDM disk from VMware
Summary: [RFE]Virt-v2v supports converting guest with RDM disk from VMware
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-v2v
Version: 9.2
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-24 07:57 UTC by mxie@redhat.com
Modified: 2023-07-07 19:10 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-07 19:10:27 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
screenshot-for-vmware-guest-with-RDM-disk (217.67 KB, application/zip)
2022-11-24 07:57 UTC, mxie@redhat.com 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-734 0 None None None 2023-07-07 19:10:26 UTC
Red Hat Issue Tracker RHELPLAN-140367 0 None None None 2022-11-24 08:11:44 UTC

Description mxie@redhat.com 2022-11-24 07:57:11 UTC 
Created attachment 1926914 [details]
screenshot-for-vmware-guest-with-RDM-disk

Description of problem:
[RFE]Virt-v2v supports converting guest with RDM disk from VMware


Version-Release number of selected component (if applicable):
virt-v2v-2.0.7-6.el9.x86_64
libguestfs-1.48.4-3.el9.x86_64
guestfs-tools-1.48.2-7.el9.x86_64
libvirt-libs-8.9.0-2.el9.x86_64
qemu-img-7.1.0-5.el9.x86_64
nbdkit-server-1.30.8-1.el9.x86_64
libnbd-1.12.6-1.el9.x86_64


How reproducible:
90%

Steps to Reproduce:
1.Prepare a guest on ESXi7.0.3 host and add a RDM disk to the guest, pls refer to sreenshots 'vmware-guest-with-RDM-disk'

2.Use virsh to dump the guest libvirtxml from VMware, can see the RDM disk info in guest libvirtxml
# virsh -c vpx://root.227.27/data/10.73.225.34/?no_verify=1 dumpxml esx7.0-rhel9.2-x86_64-with-RDM-disk
Enter root's password for 10.73.227.27: 
<domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'>
  <name>esx7.0-rhel9.2-x86_64-with-RDM-disk</name>
  .....
  <devices>
    <disk type='file' device='disk'>
      <source file='[datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64.vmdk'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='disk'>
      <source file='[datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk'/>
      <target dev='sdb' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
  ....
</domain>

3.Convert the guest from ESXi7.0.3 by v2v
# virt-v2v -ic vpx://root.227.27/data/10.73.225.34/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.3 -io vddk-thumbprint=76:75:59:0E:32:F5:1E:58:69:93:75:5A:7B:51:32:C5:D1:6D:F1:21  -ip /home/passwd  esx7.0-rhel9.2-x86_64-with-RDM-disk
[   0.2] Setting up the source: -i libvirt -ic vpx://root.227.27/data/10.73.225.34/?no_verify=1 -it vddk esx7.0-rhel9.2-x86_64-with-RDM-disk
[   3.1] Opening the source
nbdkit: vddk[1]: error: VixDiskLib_Open: [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk: Unknown error
nbdkit: vddk[1]: error: Please verify whether the "thumbprint" parameter (76:75:59:0E:32:F5:1E:58:69:93:75:5A:7B:51:32:C5:D1:6D:F1:21) 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: 2022-11-24T07:50:08.231660Z qemu-kvm: -blockdev 
{"driver":"nbd","server":{"type":"unix","path":"/tmp/v2v.ofSMud/in1"},"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:
Virt-v2v can't convert guest with RDM disk from VMware

Expected results:
As above description

Additional info:
Comment 3 Richard W.M. Jones 2022-11-24 13:45:45 UTC 
It's hard to see what the actual error is from the VDDK logs.  It
might be this:

nbdkit: vddk[1]: debug: 2022-11-24T15:58:30.936+08:00 warning -[62938] [Originator@6876 sub=vimaccess] cannot get thumbprint: SSL error code '151441516', exception: 'Wrong X.509 Certificate format'

but if it was this, I assume it would happen for any guest on the same
machine.
Comment 5 Richard W.M. Jones 2022-11-24 15:44:40 UTC 
(In reply to Richard W.M. Jones from comment #3)
> It's hard to see what the actual error is from the VDDK logs.  It
> might be this:
> 
> nbdkit: vddk[1]: debug: 2022-11-24T15:58:30.936+08:00 warning -[62938]
> [Originator@6876 sub=vimaccess] cannot get thumbprint: SSL error code
> '151441516', exception: 'Wrong X.509 Certificate format'

I compared several runs, and this message seems to happen even for
normal (successful) transfers, so this is presumably not a problem.

The actual error seems to be:

nbdkit: vddk[1]: debug: 2022-11-24T15:58:31.447+08:00 error -[62938] [Originator@6876 sub=vimaccess] GetFileName: Cannot create disk spec for disk [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk.
nbdkit: vddk[1]: debug: --> 
nbdkit: vddk[1]: debug: VixDiskLib: Error occurred when obtaining the file name for [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk. Error 1 (Unknown error) (Cannot create disk spec for disk.) at 3344.
nbdkit: vddk[1]: debug: VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk. Error 1 (Unknown error) at 7133.
nbdkit: vddk[1]: debug: VixDiskLib: VixDiskLib_Open: Cannot open disk [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk. Error 1 (Unknown error) at 7211.

There's virtually no information available online about this error.

Could it be that the guest has snapshots?
Comment 6 mxie@redhat.com 2022-11-25 03:06:30 UTC 
(In reply to Richard W.M. Jones from comment #5)
> (In reply to Richard W.M. Jones from comment #3)
> > It's hard to see what the actual error is from the VDDK logs.  It
> > might be this:
> > 
> > nbdkit: vddk[1]: debug: 2022-11-24T15:58:30.936+08:00 warning -[62938]
> > [Originator@6876 sub=vimaccess] cannot get thumbprint: SSL error code
> > '151441516', exception: 'Wrong X.509 Certificate format'
> 
> I compared several runs, and this message seems to happen even for
> normal (successful) transfers, so this is presumably not a problem.
> 
> The actual error seems to be:
> 
> nbdkit: vddk[1]: debug: 2022-11-24T15:58:31.447+08:00 error -[62938]
> [Originator@6876 sub=vimaccess] GetFileName: Cannot create disk spec for
> disk [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk.
> nbdkit: vddk[1]: debug: --> 
> nbdkit: vddk[1]: debug: VixDiskLib: Error occurred when obtaining the file
> name for [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk.
> Error 1 (Unknown error) (Cannot create disk spec for disk.) at 3344.
> nbdkit: vddk[1]: debug: VixDiskLib: VixDiskLib_OpenEx: Cannot open disk
> [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk. Error 1
> (Unknown error) at 7133.
> nbdkit: vddk[1]: debug: VixDiskLib: VixDiskLib_Open: Cannot open disk
> [datastore2] esx7.0-rhel9.2-x86_64/esx7.0-rhel9.2-x86_64_2.vmdk. Error 1
> (Unknown error) at 7211.
> 
> There's virtually no information available online about this error.
> 
> Could it be that the guest has snapshots?

The guest doesn't have snapshot, 'esx7.0-rhel9.2-x86_64_2.vmdk' is actually a iSCSI storage that is added to the guest as a RDM disk, link[1] is some info about VMware RDM and attached screenshots shows how I add a RDM disk to guest on VMware, thanks.

[1]https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-B3522FF1-76FF-419D-8DB6-F15BFD4DF12A.html
Comment 7 Richard W.M. Jones 2022-11-25 11:42:38 UTC 
We have historically not supported guests which have passthrough devices,
especially network devices.  This is the disk variation of the same thing.

It's a bit unclear what it would mean to convert a guest with a passthrough
disk.  For example, do we copy the data?  Or do we create the actual same
passthrough device on the target (which is probably not possible except in
very specific cases that would require manual intervention).

So I'm not hopeful that we would solve this any time soon.

Marking as Triaged to keep JIRA quiet.
Note You need to log in before you can comment on or make changes to this bug.