Bug 1899865

Summary: [RFE] Remove dpdk from host networking
Product: [oVirt] vdsm Reporter: Dominik Holler <dholler>
Component: GeneralAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: high    
Version: 4.40.37CC: bugs, emarcus, mperina, mtessun
Target Milestone: ovirt-4.4.4Keywords: FutureFeature
Target Release: 4.40.40Flags: pm-rhel: ovirt-4.4+
mtessun: planning_ack+
dholler: devel_ack+
mburman: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.4.4 vdsm-4.40.40 Doc Type: Removed functionality
Doc Text:
Experimental support for DPDK has been removed in Red Hat Virtualization 4.4.4.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-21 12:35:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1894022    

Description Dominik Holler 2020-11-20 09:30:23 UTC
The experimental support of using dpdk to connect host NICs to VMs was introduced in 2017 into oVirt [1].
The integration into oVirt was improved in 2018 [2].

Currently, it looks like that users never started to use this feature [3].

For this reason the integration of dpdk into oVirt should be dropped.
 


[1]
  https://blogs.ovirt.org/2017/09/ovirt-now-supports-ovs-dpdk/

[2]
  https://blogs.ovirt.org/2018/07/upgraded-dpdk-support-in-ovirt/

[3]
  https://lists.ovirt.org/archives/list/users@ovirt.org/thread/H3EVPJYR6ZAETFIA6WPSZ2E5EZIAMKB6/

Comment 2 Michael Burman 2020-12-13 10:38:49 UTC
Verified on - vdsm-4.40.40-1.el8ev.x86_64

Comment 3 Sandro Bonazzola 2020-12-21 12:35:44 UTC
This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.