Description of problem:
/usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/Target/LibVirt.pm doesn't load
Locale::TextDomain as it should caused no output any debug and no images are retrieved when converted esx images.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
/usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/Target/LibVirt.pm to add the
use Locale::TextDomain 'virt-v2v';
Add it at the top, just underneath:
use Sys::VirtV2V::UserMessage qw(user_message);
2.# export LIBGUESTFS_TRACE=1
# export LIBGUESTFS_DEBUG=1
3.# virt-v2v -f virt-v2v.conf -ic esx://10.66.91.46/?no_verify=1 -op v2v_test
virt-v2v: Failed to create storage volume: libvirt error code: 39, message: unmarshalling remote_error
4. # virsh vol-list --pool=v2v_test
failed with esx conversion
success with esx conversion
Created attachment 411861 [details]
output with using strace
The patch for this is already upstream.
Unfortunately the error message you see after patching isn't useful either because of bug # 589237.
Build 0.5.3 is in brew.
With the newest version:
Run # virt-v2v -ic esx://10.66.91.46/?no_verify=1 -op v2v_test ESX3.5-RHEL5.5-i386
The guest was converted successfully and can be boot up. No need to manual patch up /usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/Target/LibVirt.pm anymore.
Verified with virt-v2v-0.6.0-6.el5, it's fixed. Move to VERIFIED.
# virt-v2v -ic esx://10.66.91.46/?no_verify=1 -op v2v_test ESX3.5-RHEL5.5-i386
virt-v2v: ESX3.5-RHEL5.5-i386 configured with virtio drivers
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.