Created attachment 901091 [details] virt-v2v debug log Description of problem: virt-v2v of RHEL AS release 3(Taroon) VMware VM fails Version-Release number of selected component (if applicable): virt-v2v running on CentOS 6.5 x86_64 with the following RPMs installed: virt-v2v-0.9.1-5.el6_5.x86_6 libguestfs-1.20.11-2.el6.x86_64 libguestfs-tools-1.20.11-2.el6.x86_64 libguestfs-tools-c-1.20.11-2.el6.x86_64 How reproducible: Steps to Reproduce: 1. Execute virt-v2v Actual results: Fails with the following error: command: command: at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 201. at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 1152 Expected results: virt-v2v completes successfully Additional info: Attached debug log
The error is that RPM segfaults. rpm -e VMwareTools [ 82.574855] rpm[378]: segfault at ffffe344 ip 00000000007a77b4 sp 00000000ffb6c790 error 4 in ld-2.3.2.so[7a5000+15000] It could be that the RPM binary (from RHEL 3!) doesn't run under a modern kernel.
I removed the VMwareTools RPM and executed the conversion again which was completed successfully but the following errors were thrown: virt-v2v: No capability in config matches os='linux' name='virtio' distro='rhel' major='3' minor='0' virt-v2v: WARNING: /etc/fstab references unknown device /dev/cdrom. This entry must be manually fixed after conversion. virt-v2v: athspam01 configured without virtio drivers. However the VM appeared in the oVirt export domain and I was able to import to a Data Domain and boot it successfully. Should I worry for the above errors (especially the first one as the other two can be ignored in my opinion)?
(In reply to Sokratis from comment #2) > I removed the VMwareTools RPM and executed the conversion again which was > completed successfully but the following errors were thrown: > > > virt-v2v: No capability in config matches os='linux' name='virtio' > distro='rhel' major='3' minor='0' > virt-v2v: WARNING: /etc/fstab references unknown device /dev/cdrom. This > entry must be manually fixed after conversion. > virt-v2v: athspam01 configured without virtio drivers. Interesting .. I thought that the old version of virt-v2v which used the capabilities + configuration file did support RHEL 3. > However the VM appeared in the oVirt export domain and I was able to import > to a Data Domain and boot it successfully. > > Should I worry for the above errors (especially the first one as the other > two can be ignored in my opinion)? Yup, I would ignore them as long as the guest works. I'm leaving this bug open because I've not tried converting a RHEL 3 guest and it'll be interesting to see if RPM does work on the new virt-v2v.
Based on this: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.0/html-single/V2V_Guide/index.html the only supported version of Red Hat 3 is 3.9. The VM I was trying to convert runs Red Hat 3 and probably that's why the error is thrown ( I guess distro='rhel' major='3' minor='0' stands for Red Hat 3.0). Since you are mentioning the new version of virt-v2v, I wanted to ask you if there is an RPM version for CentOS 6.5 because I couldn't find any. Furthermore I couldn't find a stable version for libguestfs 1.27.
You can compile libguestfs from git on CentOS 6.5, with a bit of effort. However the first version of virt-v2v 1.27/1.28 will only be available in RHEL 7.1 and above or Fedora 21 and above. I don't think it will help with this bug in any case.
Hi Sokratis, would it be possible for you to test a newer libguestfs/v2v? virt-v2v is shipped and supported with libguestfs since v1.28, which should handle RHEL 3 as well. Since v1.35.10, virt-v2v can (hopefully) uninstall also VMware tools packages during the conversion.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days