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 2148498 - nbdkit: error: /home/vddk8.0.0/lib64/libvixDiskLib.so.7: cannot open shared object file: No such file or directory [rhel-9.1.0.z]
Summary: nbdkit: error: /home/vddk8.0.0/lib64/libvixDiskLib.so.7: cannot open shared o...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nbdkit
Version: 9.2
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: mxie@redhat.com
URL:
Whiteboard:
Depends On: 2143889
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-25 16:56 UTC by RHEL Program Management Team
Modified: 2023-02-06 07:54 UTC (History)
18 users (show)

Fixed In Version: nbdkit-1.30.8-2.el9_1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2143889
Environment:
Last Closed: 2023-01-23 15:18:40 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-140522 0 None None None 2022-11-25 17:10:09 UTC
Red Hat Knowledge Base (Solution) 6986982 0 None None None 2022-11-25 16:56:12 UTC
Red Hat Product Errata RHBA-2023:0316 0 None None None 2023-01-23 15:18:42 UTC

Comment 1 mxie@redhat.com 2022-12-01 09:00:05 UTC 
Test the bug with below builds:
virt-v2v-2.0.7-6.el9.x86_64
libguestfs-1.48.4-2.el9.x86_64
nbdkit-server-1.30.8-2.el9_1.x86_64
libvirt-libs-8.5.0-7.1.el9_1.x86_64
qemu-img-7.0.0-13.el9.x86_64
kernel-5.14.0-162.9.1.el9_1.x86_64
virtio-win-1.9.30-0.el9_1.noarch


Steps:

Scenario1: convert a guest from ESXi8.0 via vddk8.0.0 by v2v

1.1 # 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 -o libvirt -os images esx8.0-rhel8.8-x86_64
[   0.1] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-rhel8.8-x86_64
[   2.3] Opening the source
[  30.3] Inspecting the source
[  42.8] Checking for sufficient free disk space in the guest
[  42.8] Converting Red Hat Enterprise Linux 8.8 Beta (Ootpa) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 183.8] Mapping filesystem data to avoid copying unused and blank areas
[ 185.0] Closing the overlay
[ 185.3] Assigning disks to buses
[ 185.3] Checking if the guest needs BIOS or UEFI to boot
[ 185.3] Setting up the destination: -o libvirt -os images
[ 187.8] Copying disk 1/1
█ 100% [****************************************]
[ 368.9] Creating output metadata
[ 369.0] Finishing off

1.2 Check guest after finishing conversion, checkpoints of guest are passed


Scenario2: convert guests from ESXi7.0 via vddk8.0.0 by v2v

2.1 # virt-v2v -ic vpx://administrator%40vsphere.local.213.207/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io  vddk-thumbprint=09:9E:54:CF:C3:36:11:9D:7D:B6:45:E0:85:74:4D:DB:CE:24:7B:46  -ip /home/passwd  -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api  -op /home/rhvpasswd -os nfs_data esx7.0-win11-x86_64
[   0.2] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local.213.207/data/10.73.212.38/?no_verify=1 -it vddk esx7.0-win11-x86_64
[   2.0] Opening the source
[   8.6] Inspecting the source
[  15.3] Checking for sufficient free disk space in the guest
[  15.3] Converting Windows 10 Enterprise to run on KVM
virt-v2v: This guest has virtio drivers installed.
[  22.8] Mapping filesystem data to avoid copying unused and blank areas
[  25.1] Closing the overlay
[  25.4] Assigning disks to buses
[  25.4] Checking if the guest needs BIOS or UEFI to boot
[  25.4] Setting up the destination: -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[  38.5] Copying disk 1/1
█ 100% [****************************************]
[ 789.2] Creating output metadata
[ 812.1] Finishing off

2.2 Check guest after finishing conversion, checkpoints of guests are passed


Scenario3: Convert guests from ESXi6.7 via vddk8.0.0 by v2v

3.1 #  virt-v2v -ic esx://root.75.219/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=62:44:2C:4F:D0:21:0B:0D:85:7B:5D:5D:64:F8:C6:2F:4F:F0:9D:33 -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data -op /home/rhvpasswd -ip /home/esxpw esx6.7-win2022-x86_64 -b ovirtmgmt -of qcow2
[   0.1] Setting up the source: -i libvirt -ic esx://root.75.219/?no_verify=1 -it vddk esx6.7-win2022-x86_64
[   1.6] Opening the source
[   7.6] Inspecting the source
[  14.9] Checking for sufficient free disk space in the guest
[  14.9] Converting Windows Server 2022 Standard to run on KVM
virt-v2v: This guest has virtio drivers installed.
[  29.1] Mapping filesystem data to avoid copying unused and blank areas
[  31.2] Closing the overlay
[  31.5] Assigning disks to buses
[  31.5] Checking if the guest needs BIOS or UEFI to boot
[  31.5] Setting up the destination: -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[  51.8] Copying disk 1/1
█ 100% [****************************************]
[ 439.7] Creating output metadata
[ 461.5] Finishing off

3.2 Check guest after finishing conversion, checkpoints of guest are passed


Scenario4: convert guests from ESXi6.5 via vddk8.0.0 by v2v

4.1 #  virt-v2v -ic vpx://root.74.72/data/10.73.196.89/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=24:40:7E:C8:C8:1F:9C:DF:E4:E0:48:D0:9E:25:64:94:64:AF:C6:8C  -ip /home/passwd  -o rhv-upload -oc https://dell-per740-48.lab.eng.pek2.redhat.com/ovirt-engine/api -oo rhv-cluster=NFS -os nfs_data  -op /home/rhvpasswd esx6.5-rhel9.2-x86_64
[   0.0] Setting up the source: -i libvirt -ic vpx://root.74.72/data/10.73.196.89/?no_verify=1 -it vddk esx6.5-rhel9.2-x86_64
[   2.2] Opening the source
[  12.8] Inspecting the source
[  22.3] Checking for sufficient free disk space in the guest
[  22.3] Converting Red Hat Enterprise Linux 9.2 Beta (Plow) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 218.4] Mapping filesystem data to avoid copying unused and blank areas
[ 219.8] Closing the overlay
[ 220.1] Assigning disks to buses
[ 220.1] Checking if the guest needs BIOS or UEFI to boot
[ 220.1] Setting up the destination: -o rhv-upload -oc https://dell-per740-48.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[ 244.6] Copying disk 1/1
█ 100% [****************************************]
[1753.4] Creating output metadata
[1775.9] Finishing off

4.2 Check guest after finishing conversion, checkpoints of guest are passed


Result:
  The bug has been fixed.
Comment 5 mxie@redhat.com 2022-12-07 01:38:46 UTC 
Verify the bug with below builds:
virt-v2v-2.0.7-6.el9.x86_64
libguestfs-1.48.4-2.el9.x86_64
nbdkit-server-1.30.8-2.el9_1.x86_64
libvirt-libs-8.5.0-7.1.el9_1.x86_64
qemu-img-7.0.0-13.el9.x86_64
kernel-5.14.0-162.10.1.el9_1.x86_64
virtio-win-1.9.30-0.el9_1.noarch



Steps:

Scenario1: convert a guest from ESXi8.0 via vddk8.0.0 by v2v

1.1 # 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 -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api  -op /home/rhvpasswd -os nfs_data  esx8.0-rhel8.8-x86_64
[   0.1] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-rhel8.8-x86_64
[   2.3] Opening the source
[  30.3] Inspecting the source
[  42.8] Checking for sufficient free disk space in the guest
[  42.8] Converting Red Hat Enterprise Linux 8.8 Beta (Ootpa) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 183.8] Mapping filesystem data to avoid copying unused and blank areas
[ 185.0] Closing the overlay
[ 185.3] Assigning disks to buses
[ 185.3] Checking if the guest needs BIOS or UEFI to boot
[ 185.3] Setting up the destination: -o libvirt -os images
[ 187.8] Copying disk 1/1
█ 100% [****************************************]
[ 368.9] Creating output metadata
[ 369.0] Finishing off

1.2 Check guest after finishing conversion, checkpoints of guest are passed


Scenario2: convert guests from ESXi7.0 via vddk8.0.0 by v2v

2.1 # virt-v2v -ic vpx://administrator%40vsphere.local.213.207/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io  vddk-thumbprint=09:9E:54:CF:C3:36:11:9D:7D:B6:45:E0:85:74:4D:DB:CE:24:7B:46  -ip /home/passwd  -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api  -op /home/rhvpasswd -os nfs_data esx7.0-win11-x86_64
[   0.2] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local.213.207/data/10.73.212.38/?no_verify=1 -it vddk esx7.0-win11-x86_64
[   2.0] Opening the source
[   8.6] Inspecting the source
[  15.3] Checking for sufficient free disk space in the guest
[  15.3] Converting Windows 10 Enterprise to run on KVM
virt-v2v: This guest has virtio drivers installed.
[  22.8] Mapping filesystem data to avoid copying unused and blank areas
[  25.1] Closing the overlay
[  25.4] Assigning disks to buses
[  25.4] Checking if the guest needs BIOS or UEFI to boot
[  25.4] Setting up the destination: -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[  38.5] Copying disk 1/1
█ 100% [****************************************]
[ 789.2] Creating output metadata
[ 812.1] Finishing off

2.2 Check guest after finishing conversion, checkpoints of guests are passed


Scenario3: Convert guests from ESXi6.7 via vddk8.0.0 by v2v

3.1 #  virt-v2v -ic esx://root.75.219/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=62:44:2C:4F:D0:21:0B:0D:85:7B:5D:5D:64:F8:C6:2F:4F:F0:9D:33 -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data -op /home/rhvpasswd -ip /home/esxpw esx6.7-win2022-x86_64 -b ovirtmgmt -of qcow2
[   0.1] Setting up the source: -i libvirt -ic esx://root.75.219/?no_verify=1 -it vddk esx6.7-win2022-x86_64
[   1.6] Opening the source
[   7.6] Inspecting the source
[  14.9] Checking for sufficient free disk space in the guest
[  14.9] Converting Windows Server 2022 Standard to run on KVM
virt-v2v: This guest has virtio drivers installed.
[  29.1] Mapping filesystem data to avoid copying unused and blank areas
[  31.2] Closing the overlay
[  31.5] Assigning disks to buses
[  31.5] Checking if the guest needs BIOS or UEFI to boot
[  31.5] Setting up the destination: -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[  51.8] Copying disk 1/1
█ 100% [****************************************]
[ 439.7] Creating output metadata
[ 461.5] Finishing off

3.2 Check guest after finishing conversion, checkpoints of guest are passed


Scenario4: convert guests from ESXi6.5 via vddk8.0.0 by v2v

4.1 # virt-v2v -ic vpx://root.74.72/data/10.73.196.89/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=24:40:7E:C8:C8:1F:9C:DF:E4:E0:48:D0:9E:25:64:94:64:AF:C6:8C  -ip /home/passwd  -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data  -op /home/rhvpasswd esx6.5-rhel9.2-x86_64
[   0.0] Setting up the source: -i libvirt -ic vpx://root.74.72/data/10.73.196.89/?no_verify=1 -it vddk esx6.5-rhel9.2-x86_64
[   2.2] Opening the source
[  12.8] Inspecting the source
[  22.3] Checking for sufficient free disk space in the guest
[  22.3] Converting Red Hat Enterprise Linux 9.2 Beta (Plow) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 218.4] Mapping filesystem data to avoid copying unused and blank areas
[ 219.8] Closing the overlay
[ 220.1] Assigning disks to buses
[ 220.1] Checking if the guest needs BIOS or UEFI to boot
[ 220.1] Setting up the destination: -o rhv-upload -oc https://dell-per740-48.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[ 244.6] Copying disk 1/1
█ 100% [****************************************]
[1753.4] Creating output metadata
[1775.9] Finishing off

4.2 Check guest after finishing conversion, checkpoints of guest are passed


Result:
  No problems were found, move the bug from ON_QA to VERIFIED
Comment 9 errata-xmlrpc 2023-01-23 15:18:40 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (nbdkit bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:0316
Note You need to log in before you can comment on or make changes to this bug.