Bug 1595688
| Summary: | Virtio driver can't be installed on network automatically in win2012r2 guest after virt-v2v converting from vmware to libvirt on rhel7.6 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | mxie <mxie> | ||||||||||||
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | medium | ||||||||||||||
| Version: | 7.6 | CC: | jomurphy, jsuchane, juzhou, mxie, mzhan, ptoscano, tzheng, xiaodwan | ||||||||||||
| Target Milestone: | rc | Keywords: | Regression | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | V2V | ||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | |||||||||||||||
| : | 1642006 (view as bug list) | Environment: | |||||||||||||
| Last Closed: | 2019-06-25 13:32:49 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Bug Depends On: | |||||||||||||||
| Bug Blocks: | 1642006, 1649160 | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
mxie@redhat.com
2018-06-27 11:25:05 UTC
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. |