| Summary: | vmx parser cannot import more than 4 NICs [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | libvirt | Assignee: | Pino Toscano <ptoscano> |
| Status: | CLOSED ERRATA | QA Contact: | kuwei <kuwei> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.5 | CC: | dyuan, jherrman, jsuchane, kuwei, lmen, michal.skrivanek, mprivozn, mtessun, mxie, nsimsolo, ptoscano, rbalakri, tzheng, xuzhang |
| Target Milestone: | rc | Keywords: | Upstream, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-3.9.0-14.el7_5.4 | Doc Type: | Bug Fix |
| Doc Text: |
The VMX parser in libvirt did not parse more than four network interfaces. As a consequence, the esx driver did not expose more than four network interface cards (NICs) for guests running ESXi. With this update, the VMX parser parses all the available NICs in .vmx files. As a result, libvirt reports all the NICs of guests running ESXi.
|
Story Points: | --- |
| Clone Of: | 1560917 | Environment: | |
| Last Closed: | 2018-05-14 16:11:44 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1560917 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-04-12 13:10:50 UTC
Try to verify the bug with below builds:
libvirt-3.9.0-14.el7_5.4.x86_64
virt-v2v-1.36.10-6.el7_5.2.x86_64
qemu-kvm-rhev-2.10.0-21.el7_5.2.x86_64
Test steps：
Scenario 1:
1.Prepare a rhel7.4 guest on ESXi 6.5 with 10 NIC.
2.Using virsh dumpxm the guest xml.
#virsh -c vpx://root@vcenter/data/ESXi/?no_verify=1
virsh # dumpxml esx6.5-rhel7.4-x64-vmware-tools
..................
<interface type='bridge'>
<mac address='00:50:56:a2:fc:be'/>
<source bridge='VM Network'/>
<model type='vmxnet3'/>
</interface>
.................
<interface type='bridge'>
<mac address='00:50:56:a2:6e:0e'/>
<source bridge='VM Network'/>
<model type='e1000e'/>
.......................
3.Using virt-v2v to convert the guest to kvm and RHV
4.From Steps 2, all the NIC could be list, from steps 3, the guest could converted by virt-v2v and all the NIC could list.
Scenario 2:
1.Prepare a rhel7.4 guest on ESXi 6.0/5.5/5.1 with 10 NIC.
2.Using virsh dumpxml the guest xml.
3.Using virt-v2v to convert the guest to kvm and RHV
4.From Steps 2, all the NIC could be list, from steps 3, the guest could converted by virt-v2v and all the NIC could list.
Scenario 3:
1.Prepare a rhel7.4 guest on ESXi 6.5 with 10 NIC(5 e1000, 5 VMXNET3).
2.Using virsh dumpxml the guest xml.
3.Using virt-v2v to convert the guest to kvm and RHV
4.From Steps 2, all the NIC could be list, from steps 3, the guest could converted and all the NIC could list.
Scenario 3:
1.Prepare a windows10 guest on ESXi 6.5 with 10 NIC(5 e1000, 5 VMXNET3).
2.Using virsh dumpxml the guest xml.
3.Using virt-v2v to convert the guest to kvm and RHV
4.From Steps 2, all the NIC could be list, from steps 3, the guest could converted and all the NIC could list.
So, I think the bug has been fix, move the bug to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1396 |