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.

Description of problem:
nbdinfo output to stdout instead of stderr during virt-v2v conversion

Version-Release number of selected component (if applicable):
Virt-p2v-1.40.2-1.el7.iso
libvirt-8.0.0-1.el9.x86_64
libguestfs-1.46.1-2.el9.x86_64
qemu-kvm-6.2.0-4.el9.x86_64
virt-v2v-1.45.97-2.el9.x86_64
virtio-win-1.9.19-5.el9_b.noarch
nbdkit-1.28.4-2.el9.x86_64
libnbd-1.10.3-1.el9.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Launch RHEL7 virt-p2v client, connect to RHEL9 server.
2.Use virt-p2v to convert.

Actual results:
The conversion hangs after copying disk, there is nbdinfo showed in virt-p2v client.

Expected results:
The conversion can be finished successfully and no nbdinfo showed in virt-p2v client.

Additional info:
logs:http://fileshare.englab.nay.redhat.com/pub/section3/libvirtmanual/tzheng/virt-p2v-20220124-6e0cxsb6/

Patch posted:
https://listman.redhat.com/archives/libguestfs/2022-January/msg00168.html

I tested this myself and it works for me.

Fixed upstream in:
https://github.com/libguestfs/virt-v2v/commit/68af35d48ca845133ede948d36ee351d171e3de8

Tested the bug with:
Virt-p2v-1.40.2-1.el7.iso
libguestfs-1.46.1-2.el9.x86_64
virt-v2v-1.45.97-3.el9.x86_64
nbdkit-1.28.5-1.el9.x86_64
libvirt-8.0.0-2.el9.x86_64
qemu-kvm-6.2.0-5.el9.x86_64

1.Launch RHEL7 virt-p2v client, connect to RHEL9 server.
2.Use virt-p2v to start conversion to local kvm and RHV, check the information printed in virt-p2v client,there is no nbdinfo showed in virt-p2v client.

Refer to the above comments, move the bug to VERIFIED.

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 (new packages: virt-v2v), 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/RHEA-2022:2566