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 1595688 - Virtio driver can't be installed on network automatically in win2012r2 guest after virt-v2v converting from vmware to libvirt on rhel7.6
Summary: Virtio driver can't be installed on network automatically in win2012r2 guest ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.6
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: V2V
Depends On:
Blocks: 1642006 1649160
TreeView+ depends on / blocked
 
Reported: 2018-06-27 11:25 UTC by mxie@redhat.com
Modified: 2019-06-25 13:32 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1642006 (view as bug list)
Environment:
Last Closed: 2019-06-25 13:32:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (75.21 KB, image/png)
2018-06-27 11:25 UTC, mxie@redhat.com 		no flags Details
v2v.log (1.01 MB, text/plain)
2018-06-27 11:25 UTC, mxie@redhat.com 		no flags Details
esx5.5-win2012r2-to-libvirt.xml (1.34 KB, application/xml)
2018-06-28 02:38 UTC, mxie@redhat.com 		no flags Details
win2012r2-import-libvirt.xml (3.28 KB, text/plain)
2018-06-28 03:19 UTC, mxie@redhat.com 		no flags Details
v2v-win2012r2-qemu-kvm-rhev-2.10.0-21.el7_5.2.log (1.00 MB, text/plain)
2018-07-31 14:40 UTC, mxie@redhat.com 		no flags Details
View All

Description mxie@redhat.com 2018-06-27 11:25:05 UTC 
Created attachment 1455021 [details]
screenshot

Description of problem:
Virtio driver can't be installed on network automatically in win2012r2 guest after virt-v2v converting from vmware to libvirt on rhel7.6

Version-Release number of selected component (if applicable):
kernel: 3.10.0-906.el7.x86_64
virt-v2v-1.38.2-5.el7.x86_64
libguestfs-1.38.2-5.el7.x86_64
libvirt-4.4.0-2.el7.x86_64
qemu-kvm-rhev-2.12.0-5.el7.x86_64
qemu-kvm-1.5.3-157.el7.x86_64
virtio-win-1.9.4-2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1.Convert win2012r2 guest from vmware to libvirt by virt-v2v on rhel7.6
# /bin/virt-v2v  -ic vpx://root.75.182/data/10.73.3.19/?no_verify=1 -o local -os /home -of raw -b virbr0 esx5.5-win2012r2-x86_64 -on v2v-esx5.5-win2012r2-x86_64-qemu-kvm-rhev --password-file /tmp/v2v_vpx_passwd -v -x |& tee > v2v-esx5.5-win2012r2-x86_64-qemu-kvm-rhev.log

2.Power on guest after converting and find guest's network device has no driver, pls refer to screenshot.

3.This problem is also found in v2v auto testing
https://libvirt-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/v2v/view/RHEL-7.6/job/v2v-RHEL-7.6-runtest-x86_64-acceptance-libvirt/9/testReport/


Actual results:
As above description

Expected results:
Virtio driver can be installed on network normally in win2012r2 guest after virt-v2v converting from vmware to libvirt on rhel7.6

Additional info:
1.Can't reproduce the problem if convert win2012r2 guest from vmware to rhv4.2 on rhel7.6
2.Can't reproduce the problem with same virt-v2v rhel7.6 builds on rhel7.5 kernel, so this regression bug may be caused by kernel
virt-v2v-1.38.2-5.el7.x86_64
libguestfs-1.38.2-5.el7.x86_64
libvirt-4.4.0-2.el7.x86_64
qemu-kvm-rhev-2.12.0-5.el7.x86_64
kernel:3.10.0-862.el7.x86_64
virtio-win-1.9.4-2.el7.noarch
Comment 3 mxie@redhat.com 2018-06-27 11:25:35 UTC 
Created attachment 1455022 [details]
v2v.log
Comment 4 Pino Toscano 2018-06-27 17:31:32 UTC 
I see that -o local is used: can you please provide
a) the libvirt XML that virt-v2v generates after the conversion
b) the XML of the libvirt guest once it is imported in libvirt
?
Comment 5 mxie@redhat.com 2018-06-28 02:38:52 UTC 
Created attachment 1455165 [details]
esx5.5-win2012r2-to-libvirt.xml
Comment 6 mxie@redhat.com 2018-06-28 03:18:58 UTC 
1. "esx5.5-win2012r2-to-libvirt.xml"is the one virt-v2v generates after the conversion

2. "win2012r2-import-libvirt.xml" is the XML of the libvirt guest once it is imported in libvirt
Comment 7 mxie@redhat.com 2018-06-28 03:19:24 UTC 
Created attachment 1455182 [details]
win2012r2-import-libvirt.xml
Comment 8 Pino Toscano 2018-07-30 13:48:34 UTC 
Is it still an issue?  I don't see how the host kernel can make a difference in the installation of the virtio drivers.

(In reply to mxie from comment #0)
> 2.Can't reproduce the problem with same virt-v2v rhel7.6 builds on rhel7.5
> kernel, so this regression bug may be caused by kernel

Can you please attach a v2v log of this setup?
Comment 9 mxie@redhat.com 2018-07-31 14:40:18 UTC 
(In reply to Pino Toscano from comment #8)
> Is it still an issue?  I don't see how the host kernel can make a difference
> in the installation of the virtio drivers.
> 
> (In reply to mxie from comment #0)
> > 2.Can't reproduce the problem with same virt-v2v rhel7.6 builds on rhel7.5
> > kernel, so this regression bug may be caused by kernel
> 
> Can you please attach a v2v log of this setup?

It's strange that I can reproduce bug with virt-v2v rhel7.6 builds on rhel7.5 kernel today
virt-v2v-1.38.2-10.el7.x86_64
libguestfs-1.38.2-10.el7.x86_64
libvirt-4.5.0-5.el7.x86_64
qemu-kvm-rhev-2.12.0-8.el7.x86_64
virtio-win-1.9.4-2.el7.noarch
kernel-3.10.0-843.el7.x86_64


But I found virtio driver can be installed on network automatically in win2012r2 guest after virt-v2v converting to libvirt with below builds (only downgrade qemu-kvm-rhev from 2.12.0-8 to 2.10.0-21.el7_5.2), pls check the log "v2v-win2012r2-qemu-kvm-rhev-2.10.0-21.el7_5.2.log"

virt-v2v-1.38.2-10.el7.x86_64
libguestfs-1.38.2-10.el7.x86_64
libvirt-4.5.0-5.el7.x86_64
qemu-kvm-rhev-2.10.0-21.el7_5.2.x86_64
kernel-3.10.0-924.el7.x86_64
virtio-win-1.9.4-2.el7.noarch

So I'm not sure the bug is caused by which component, sorry~
Comment 10 mxie@redhat.com 2018-07-31 14:40:51 UTC 
Created attachment 1471862 [details]
v2v-win2012r2-qemu-kvm-rhev-2.10.0-21.el7_5.2.log
Comment 12 Jaroslav Suchanek 2019-06-25 13:32:49 UTC 
This issue will be addressed in next major release of RHEL.
Note You need to log in before you can comment on or make changes to this bug.