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
Created attachment 1455022 [details] v2v.log
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 ?
Created attachment 1455165 [details] esx5.5-win2012r2-to-libvirt.xml
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
Created attachment 1455182 [details] win2012r2-import-libvirt.xml
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?
(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~
Created attachment 1471862 [details] v2v-win2012r2-qemu-kvm-rhev-2.10.0-21.el7_5.2.log
This issue will be addressed in next major release of RHEL.