Bug 1155121

Summary: Virt-v2v will fail when using relative path for -i ova
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: codong, dyuan, juzhou, mbooth, mzhan, ptoscano, rjones
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: V2V
Fixed In Version: libguestfs-1.28.1-1.4.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 13:46:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Detailed log file none

Description tingting zheng 2014-10-21 12:03:48 UTC 
Created attachment 948906 [details]
Detailed log file

Description
Virt-v2v will fail when using relative path for -i ova

Version:
virt-v2v-1.28.1-1.2.el7.x86_64
libguestfs-1.28.1-1.2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a directory containing the esx ova files.
# pwd
/var/lib/libvirt/images

# ls esx-rhel6
esx-rhel6-disk1.vmdk  esx-rhel6.mf  esx-rhel6.ovf

2.Use virt-v2v to convert the ova file,input a relative path.
# virt-v2v -i ova -os default esx-rhel6 -of raw 
[   0.0] Opening the source -i ova esx-rhel6
[   0.0] Creating an overlay to protect the source from being modified
[   0.0] Opening the overlay
virt-v2v: error: libguestfs error: guestfs_launch failed.
This usually means the libguestfs appliance failed to start or crashed.
See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
or run 'libguestfs-test-tool' and post the *complete* output into a
bug report or message to the libguestfs mailing list.

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]

If I put the absolute path,virt-v2v works well.

Actual results：
Virt-v2v will fail when using relative path for -i ova

Expected results:
Virt-v2v didn't fail when using relative path for -i ova

Additional info:
1.Attach the debug info.
Comment 2 Richard W.M. Jones 2014-10-21 12:37:47 UTC 
Upstream fix:
https://github.com/libguestfs/libguestfs/commit/e1eccae2da3a670c1ef7626c8779b71fb1877f7d
Comment 4 tingting zheng 2014-10-28 04:50:03 UTC 
Tested with:
virt-v2v-1.28.1-1.5.el7.x86_64
libguestfs-1.28.1-1.5.el7.x86_64

# virt-v2v -i ova -os default esx-rhel6 -of raw
[   0.0] Opening the source -i ova esx-rhel6
[   0.0] Creating an overlay to protect the source from being modified
[   1.0] Opening the overlay
[  10.0] Initializing the target -o libvirt -os default
[  10.0] Inspecting the overlay
[  23.0] Checking for sufficient free disk space in the guest
[  23.0] Estimating space required on target for each disk
[  23.0] Converting Red Hat Enterprise Linux Server release 6.5 (Santiago) to run on KVM
virt-v2v: warning: /files/boot/grub/device.map/hd0 references unknown 
device "sda".  You may have to fix this entry manually after conversion.
virt-v2v: warning: /files/etc/sysconfig/grub/boot references unknown device 
"sda".  You may have to fix this entry manually after conversion.
virt-v2v: This guest has virtio drivers installed.
[  94.0] Mapping filesystem data to avoid copying unused and blank areas
[  95.0] Closing the overlay
[  96.0] Copying disk 1/1 to /var/lib/libvirt/images/esx-rhel6-sda (raw)
    (100.00/100%)
[ 166.0] Creating output metadata
Pool default refreshed

Domain esx-rhel6 defined from /tmp/v2vlibvirt44c89b.xml

[ 167.0] Finishing off

Refer to the above comments,ova file with relative path can be converted successfully by virt-v2v,so move the bug to VERIFIED.
Comment 6 errata-xmlrpc 2015-03-05 13:46:42 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, 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://rhn.redhat.com/errata/RHBA-2015-0303.html