Bug 1642014

Summary:	RFE: virt-v2v: allow libvirt backend for xen+ssh
Product:	Red Hat Enterprise Linux 9	Reporter:	mxie <mxie>
Component:	virt-v2v	Assignee:	Virtualization Maintenance <virt-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.0	CC:	aoconnor, jsuchane, juzhou, knoel, mxie, mzhang, ptoscano, rjones, spower, tgolembi, tzheng, virt-bugs, xiaodwan, zili
Target Milestone:	beta	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	V2V
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1435162	Environment:
Last Closed:	2021-04-27 16:02:18 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:
Bug Depends On:	1140166, 1435162
Bug Blocks:	1370055, 1473046

Description mxie@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 3 RHEL 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 4 Richard 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 5 Richard 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 6 Tomáš 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 7 Richard W.M. Jones 2021-04-28 09:26:08 UTC

Maybe bug 1904946?

Comment 8 mxie@redhat.com 2021-04-29 10:55:30 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 9 Richard 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.