Bug 2147528
| Summary: | [RFE]Virt-v2v supports converting guest with RDM disk from VMware | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | mxie <mxie> | ||||
| Component: | virt-v2v | Assignee: | Virtualization Maintenance <virt-maint> | ||||
| Status: | CLOSED MIGRATED | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 9.2 | CC: | chhu, hongzliu, juzhou, lersek, mzhan, rjones, tyan, tzheng, vwu, xiaodwan | ||||
| Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-07-07 19:10:27 UTC | Type: | Feature Request | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
mxie@redhat.com
2022-11-24 07:57:11 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. (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? (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 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. |