Description of problem: VDSM report VF as dpdk as a free interface while the VM is running "dpdk0": { "ipv6autoconf": false, "addr": "", "dhcpv6": false, "ipv6addrs": [], "ipv4addrs": [], "mtu": "", "dhcpv4": false, "netmask": "", "ipv4defaultroute": false, "pciaddr": "0000:05:10.0", "hwaddr": "02:00:00:00:00:00", "ipv6gateway": "::", "gateway": "" }, Version-Release number of selected component (if applicable): vdsm-4.20.1-67.git4721d69.el7.centos.x86_64 How reproducible: 100 Steps to Reproduce: 1. Create network with Passthrough 2. Set num of VF 1 3. Add VF to VM 4. Start VM 5. run vdsm-client Host getCapabilities on VDSM Actual results: VDSM report VF as dpdk Expected results: VDSM shouldn't report VF as dpdk
The fix has already been merged to master.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Verified on - vdsm-4.20.1-180.git07508e2.el7.centos.x86_64 and 4.2.0-0.0.master.20170712143425.gitcb02bb5.el7.centos
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.