Hide Forgot
Created attachment 414509 [details] after conversion /etc/module.conf Description of problem: V2V doesn't convert network driver for some guests(ESX4.0-rhel3u9-32bit) Before conversion, /etc/module.conf alias eth0 pcnet32 alias scsi_hostadapter mptbase alias scsi_hostadapter1 mptscsih lsmod |grep pcnet pcnet32 22820 1 mii 4664 0 [pcnet32] crc32 3764 0 [pcnet32] Version-Release number of selected component (if applicable): v2v-libvirt-0.8.1-1.el5 virt-v2v-0.5.4-1.el5 How reproducible: always Steps to Reproduce: 1.#virt-v2v -f virt-v2v.conf -ic esx://host/?no_verify=1 -o rhev -osd nfs:/export ESX4.0-RHEL3.9-i386; Actual results: network driver isn't converted to e1000 Expected results: network driver isn converted to e1000 Additional info:
Created attachment 414512 [details] after conversion, #lsmod
Created attachment 414517 [details] the similar problems in xenhvm guest: rhel3u9-32 bit and 64bit In xenhvm guest: rhel3u9-32 bit and 64bit, after conversion, "8139cp device eth0 " won't be converted to e1000.
this also happen to ESX3.5-rhel3u9-32bit, after conversion, /etc/modules.conf, alias eth0 pcnet32 alias scsi_hostadapter mptbase alias scsi_hostadapter1 mptscsih the correct should be, [root@dhcp-66-83-46 root]# cat /etc/modules.conf alias eth0 e1000 alias scsi_hostadapter mptbase alias scsi_hostadapter1 mptscsih
Created attachment 414804 [details] log from LIBGUESTFS_TRACE=1 during conversion
I've tracked this down to an issue in libguestfs.
Version 0.6.0-2 has a dependency on the updated libguestfs.
Verified in v2v 0.6.0-2 and libguestfs-1.2.7-1.el5.3. Now it is changed to e1000(rhel3u9-64-xenhvm) # cat /etc/modules.conf alias eth0 e1000
This issue was already fixed in advisory http://rhn.redhat.com/errata/RHEA-2010-0495.html