Hide Forgot
Description of problem: winxp-32b from xen to libvirt pool can not find useable network driver. the device manager has a yellow exclamation mark. the guest's network is good before conversion Version-Release number of selected component (if applicable): augeas-libs-0.7.2-4.el6.x86_64 febootstrap-2.11-6.el6.x86_64 febootstrap-supermin-helper-2.11-6.el6.x86_64 fence-virtd-libvirt-0.2.1-5.el6.x86_64 hivex-1.2.4-3.el6.x86_64 libguestfs-1.7.17-12.el6.x86_64 libguestfs-tools-1.7.17-12.el6.x86_64 libguestfs-winsupport-1.0-5.el6.x86_64 libvirt-0.8.7-5.el6.x86_64 virtio-win-1.1.16-0.el6.noarch virt-v2v-0.7.1-2.el6.x86_64 How reproducible: Steps to Reproduce: 1.virt-v2v -ic xen+ssh://10.66.72.123 -op sdb1 -b breth0 winxp-32b 2.check the guest network driver after conversion Actual results: the guest's network driver is bad and it can't connect internet. Expected results: the guest's network driver is good and it can connect internet. Additional info: this bug can be reproduced from xen to rhevm .
Created attachment 478009 [details] winxp-network-driver
I have replicated this with a libvirt->libvirt conversion. The reason is that virtio-win doesn't contain a netkvm driver for Windows XP. A closer inspection also reveals there is no netkvm driver for Windows 7 32bit and 64bit, and that there are only 32bit drivers for Windows XP.
I've pushed a fix for this upstream.
verify this bug in rhel6: virt-v2v-0.7.1-3.el6.x86_64 libguestfs-1.7.17-12.el6.x86_64 libguestfs-*-1.7.17-12.el6.x86_64 libvirt-0.8.7-6.el6.x86_64 febootstrap-2.11-6.el6.x86_64 hivex-1.2.4-3.el6.x86_64 libguestfs-winsupport-1.0-5.el6.x86_64 augeas-libs-0.7.2-4.el6.x86_64 1)#virt-v2v -ic xen+ssh://10.66.72.123 -op sdb1 -b breth0 winxp-32bit winxp-32bit.img: 100% [===========================================================================================================================]D 0h03m28s virt-v2v: WARNING: There is no virtio net driver available in the directory specified for this version of Windows. The guest will be configured with a rtl8139 network adapter, but no driver will be installed for it. If the rtl8139 driver is not already installed in the guest, you must install it manually after conversion. virt-v2v: winxp-32bit configured with virtio storage only. 2) check the guest network driver is RTL8139 and network is fine storage driver is virtio
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: virt-v2v now enables the conversion of Windows guests which do not have available VirtIO drivers, although these guests are not guaranteed to operate correctly after conversion.
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. http://rhn.redhat.com/errata/RHBA-2011-0650.html