RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 676553 - Convert winxp-32b from xen to kvm the guest can not find useable network driver
Summary: Convert winxp-32b from xen to kvm the guest can not find useable network driver
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-v2v
Version: 6.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Matthew Booth
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-10 08:35 UTC by Huang Wenlong
Modified: 2015-09-28 02:10 UTC (History)
3 users (show)

Fixed In Version: virt-v2v-0.7.1-3.el6
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2011-05-19 13:54:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
winxp-network-driver (62.54 KB, image/png)
2011-02-10 08:36 UTC, Huang Wenlong 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0650 0 normal SHIPPED_LIVE virt-v2v and augeas bug fix update 2011-07-01 15:27:50 UTC

Description Huang Wenlong 2011-02-10 08:35:28 UTC 
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 .
Comment 1 Huang Wenlong 2011-02-10 08:36:10 UTC 
Created attachment 478009 [details]
winxp-network-driver
Comment 3 Matthew Booth 2011-02-10 10:53:07 UTC 
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.
Comment 4 Matthew Booth 2011-02-11 16:00:25 UTC 
I've pushed a fix for this upstream.
Comment 5 Huang Wenlong 2011-02-15 05:41:24 UTC 
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
Comment 8 Laura Bailey 2011-04-27 07:10:48 UTC 
    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.
Comment 9 errata-xmlrpc 2011-05-19 13:54:21 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.