Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Descriptionmxie@redhat.com
2018-10-23 11:46:37 UTC
Can reproduce the bug with builds,so clone the bug from rhel7
virt-v2v-1.38.4-5.el8+2078+2754d2d2.x86_64
libguestfs-1.38.4-5.el8+2078+2754d2d2.x86_64
libvirt-client-4.5.0-12.el8+2115+e415383f.x86_64
qemu-kvm-2.12.0-41.el8+2104+3e32e6f8.x86_64
+++ This bug was initially created as a clone of Bug #1435162 +++
+++ This bug was initially created as a clone of Bug #1379240 +++
Description of problem:
virt-v2v should not report error any more since libvirt bug 1134592 has been fixed
Version-Release number of selected component (if applicable):
virt-v2v-1.32.7-3.el7.x86_64
libvirt-2.0.0-10.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Run below virt-v2v command.
# virt-v2v -ic xen+ssh://10.73.3.21 -o rhev -os 10.73.2.1:/home/nfs_export --network rhevm xen-hvm-win7-x86_64 -of raw
[ 0.0] Opening the source -i libvirt -ic xen+ssh://10.73.3.21 xen-hvm-win7-x86_64
virt-v2v: error: because of libvirt bug
https://bugzilla.redhat.com/show_bug.cgi?id=1134592 you must set this
environment variable:
export LIBGUESTFS_BACKEND=direct
and then rerun the virt-v2v command.
If reporting bugs, run virt-v2v with debugging enabled and include the
complete output:
virt-v2v -v -x [...]
Actual results:
as above
Expected results:
virt-v2v should be ran successfully.
Additional info:
------------------------
The fix for bug 1379240 affected only VMware input -- ssh connection via libvirt is affected by bug 1140166.
Thus, this bug will track the status of using the libvirt backend for xen+ssh input sources.
Comment 3RHEL Program Management
2021-02-15 07:43:40 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 4Richard W.M. Jones
2021-02-15 09:10:20 UTC
I'm sorry, this bug was closed in error by the "stale bugs" process.
Comment 5Richard W.M. Jones
2021-04-27 16:02:18 UTC
This is fixed upstream in commit 4c795c5a53e2d55b70c5b1620b57dfc09884cea8
which has been in virt-v2v since 1.40.
Comment 6Tomáš Golembiovský
2021-04-28 09:06:11 UTC
If I recall there is still an issue that Xen input cannot be used with libvirt 6.0 and newer. Disk format information is required for backing image and this is not provided by Xen input. Has this also been fixed?
Comment 7Richard W.M. Jones
2021-04-28 09:26:08 UTC
Hi Richard,
I think the bug isn't fixed yet, please check below result:
# rpm -q virt-v2v libguestfs
virt-v2v-1.42.0-11.module+el8.5.0+10793+d881d728.x86_64
libguestfs-1.44.0-3.module+el8.5.0+10681+17a9b157.x86_64
# virt-v2v -ic xen+ssh://root.224.33 xen-hvm-rhel7.9-x86_64 -of qcow2
virt-v2v: error: because of libvirt bug https://bugzilla.redhat.com/1140166
you must set this environment variable:
export LIBGUESTFS_BACKEND=direct
and then rerun the virt-v2v command.
If reporting bugs, run virt-v2v with debugging enabled and include the
complete output:
virt-v2v -v -x [...]
Comment 9Richard W.M. Jones
2021-04-29 11:01:44 UTC
Oh I see. This was actually fixed in 1.43.4, so the fix is not
in RHEL 8. I'm going to move this bug to RHEL 9 because
there's a simple, documented workaround for RHEL 8 already,
and I just did a virt-v2v build for RHEL AV and I hope that
most development & QE effort can move to RHEL 9.
The bug status stays the same because it's fixed (or will be
very soon) in RHEL 9.