Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1868115

Summary:	[RFE] Enable e1000 PMD support in downstream OVS-DPDK deployment
Product:	Red Hat OpenStack	Reporter:	Paras Babbar <pbabbar>
Component:	openvswitch	Assignee:	Open vSwitch development team <ovs-team>
Status:	CLOSED WONTFIX	QA Contact:	Eran Kuris <ekuris>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16.1 (Train)	CC:	akaris, apevec, chrisw, fleitner, jlibosva, ktraynor, rhos-maint, smooney, supadhya
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-18 18:22:13 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 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