Bug 1684605

Summary: QEDE not working as non-privileged user on RHEL8
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Kevin Traynor <ktraynor>
Component: openvswitch2.11Assignee: Kevin Traynor <ktraynor>
Status: CLOSED ERRATA QA Contact: Jean-Tsung Hsiao <jhsiao>
Severity: medium Docs Contact:
Priority: medium    
Version: FDP 19.03CC: arahman, ctrautma, jhsiao, mchopra, pvauter, qding, ralongi, rasesh.mody, rkhan, shahed.shaikh, tredaelli
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openvswitch2.11-2.11.0-8.el8fdn.src.rpm Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-05 14:55:04 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:

Description Kevin Traynor 2019-03-01 15:57:59 UTC 
Qede pmd driver does not report the RTE_PCI_DRV_IOVA_AS_VA flag.

This means that access to /proc/self/pagemap is needed, however since Linux 4.x it is not allowed to non-root users without CAP_SYS_ADMIN privileges which openvswitch currently does not have.

TBC, this may be able to fixed by adding the flag to the Qede pmd similar to what is done in http://patchwork.dpdk.org/patch/50274/
Comment 1 Kevin Traynor 2019-03-01 16:09:46 UTC 
Rasesh, can you confirm that it is ok for Qede pmd to report this flag? If so, I can send a patch for it.
Comment 3 Rasesh Mody 2019-03-07 01:05:47 UTC 
(In reply to Kevin Traynor from comment #1)
> Rasesh, can you confirm that it is ok for Qede pmd to report this flag? If
> so, I can send a patch for it.

Kevin, it is ok for QEDE PMD to report this flag, please send a patch with the change.
Comment 4 Kevin Traynor 2019-03-07 18:47:19 UTC 
Checked initialisation on RHEL8 with test openvswitch2.11 rpm and sent patch upstream http://patchwork.dpdk.org/patch/50974/
Comment 17 errata-xmlrpc 2019-06-05 14:55:04 UTC 
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/RHBA-2019:1386