Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1578003 - [fdProd] Enable QEDE PMD on x86_64
[fdProd] Enable QEDE PMD on x86_64
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openvswitch (Show other bugs)
7.6
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Timothy Redaelli
Jean-Tsung Hsiao
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-14 11:16 EDT by Timothy Redaelli
Modified: 2018-06-21 09:37 EDT (History)
5 users (show)

See Also:
Fixed In Version: openvswitch-2.9.0-36.el7fdn
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-21 09:36:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1962 None None None 2018-06-21 09:37 EDT

  None (edit)
Description Timothy Redaelli 2018-05-14 11:16:33 EDT

    
Comment 4 Jean-Tsung Hsiao 2018-05-20 22:26:57 EDT
Hi Tim,

Can I test this bug with openvswitch-2.9.0-36.el7fdp.x86_64 ?

Thanks!

Jean
Comment 6 Jean-Tsung Hsiao 2018-05-21 11:43:19 EDT
On "systemctl start openvswitch" qede was initialized by OVS:

2018-05-21T15:38:41.494Z|00027|dpdk|INFO|EAL: PCI device 0000:85:00.0 on NUMA socket 1
2018-05-21T15:38:41.494Z|00028|dpdk|INFO|EAL:   probe driver: 1077:1656 net_qede
2018-05-21T15:38:41.496Z|00029|dpdk|INFO|EAL:   using IOMMU type 1 (Type 1)
2018-05-21T15:38:42.147Z|00030|dpdk|INFO|EAL: PCI device 0000:85:00.1 on NUMA socket 1
2018-05-21T15:38:42.147Z|00031|dpdk|INFO|EAL:   probe driver: 1077:1656 net_qede

[root@netqe9 ~]# rpm -q openvswitch
openvswitch-2.9.0-37.el7fdp.x86_64

Set the status to VERIFIED.
Comment 8 errata-xmlrpc 2018-06-21 09:36:35 EDT
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-2018:1962

Note You need to log in before you can comment on or make changes to this bug.