Bug 1615392 - Switch nbdkit-plugin-vddk to use VixDiskLib_AllocateConnectParams
Summary: Switch nbdkit-plugin-vddk to use VixDiskLib_AllocateConnectParams
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nbdkit
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: V2V
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-13 13:49 UTC by Richard W.M. Jones
Modified: 2019-06-05 21:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-05 21:51:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2018-08-13 13:49:53 UTC
Description of problem:

With VDDK 6.7 we get this warning:

nbdkit: error: VixDiskLib: VixDiskLibIsLegacyConnParams: the instance of VixDiskLibConnectParams is NOT allocated by VixDiskLib_AllocateConnectParams. The new features in 6.7 or later are not supported.

It falls back to using the legacy path so this is not a
problem, but at some point we should switch to using
VixDiskLib_AllocateConnectParams

Version-Release number of selected component (if applicable):

nbdkit 1.2.6-1.el7

How reproducible:

100%

Steps to Reproduce:
1. Run virt-v2v with ‘-it vddk’ source.

Make sure you have the ‘-v -x’ flags set too so you can see
VDDK debugging messages.

Make sure you are using VDDK >= 6.7

Actual results:

You will see the warning above.

Expected results:

If using VixDiskLib_AllocateConnectParams then the warning
should not be printed and presumably extra features are
possible.

Additional info:

"New Connect Parameters and Functions" in
https://vdc-download.vmware.com/vmwb-repository/dcr-public/8f96698a-0e7b-4d67-bb6c-d18a1d101540/d326003d-55b9-4b15-babc-1adfdc69a4a2/vsphere-vddk-67-programming-guide.pdf

Comment 2 Richard W.M. Jones 2019-04-05 09:13:14 UTC
Upstream in 61e11b41597f80a5e8b629a5dd320cd62c3e8a59, nbdkit 1.12.

Seems unlikely we'll get this for RHEL 7, but could happen for RHEL 8.1.0.

Comment 3 Richard W.M. Jones 2019-06-05 21:51:42 UTC
We're not going to fix this in RHEL 7, but it's already fixed in RHEL 8.1.


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