Bug 1868115 - [RFE] Enable e1000 PMD support in downstream OVS-DPDK deployment
Summary: [RFE] Enable e1000 PMD support in downstream OVS-DPDK deployment
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Open vSwitch development team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-11 17:49 UTC by Paras Babbar
Modified: 2023-05-11 11:33 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-18 18:22:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NFV-1742 0 None None None 2023-05-11 11:33:00 UTC
Red Hat Issue Tracker OSP-22493 0 None None None 2023-02-18 02:40:35 UTC

Description Paras Babbar 2020-08-11 17:49:28 UTC
Description of problem:

The VM was not able to reach the external network as prompting an error below:

2020-08-10T18:28:48.892Z|00331|dpdk|ERR|Invalid port_id=128
2020-08-10T18:28:48.903Z|00332|dpdk|ERR|EAL: Driver cannot attach the device (0000:02:03.0)
2020-08-10T18:28:48.903Z|00333|dpdk|ERR|EAL: Failed to attach device on primary process
2020-08-10T18:28:48.903Z|00334|netdev_dpdk|WARN|Error attaching device '0000:02:03.0' to DPDK
2020-08-10T18:28:48.903Z|00335|netdev|WARN|dpdk1: could not set configuration 

This is most likely due to the e1000 is not enabled in downstream jobs.

Version-Release number of selected component (if applicable):

RHOSP16.1

openvswitch2.13-2.13.0-39.el8fdp.x86_64
network-scripts-openvswitch2.13-2.13.0-39.el8fdp.x86_64
openvswitch-selinux-extra-policy-1.0-22.el8fdp.noarch
rhosp-openvswitch-2.13-8.el8ost.noarch

How reproducible:
Always

Steps to Reproduce:
1.deploy openstack with e1000 nic rather than virtio
2. To be able to run ovs-dpdk in a nested virt env we enable the iommu to allow vfio-cpi to work 
using 
 --qemu-commandline='-machine kernel-irqchip=split -device
   > intel-iommu,intremap=on,caching-mode=on' --machine=q35"


Actual results:

Error attaching device '0000:02:03.0' to DPDK
Expected results:
Attached device '0000:02:03.0' to DPDK

Additional info:

Comment 1 Flavio Leitner 2020-08-18 18:22:13 UTC
I am closing this bug based on an e-mail discussion where the old e1000 could be replaced by supported virtio.
Thanks
fbl


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