Bug 2025649 - [vDPA] can't whitelist by device address because of 2 layers of vdpa devices
Summary: [vDPA] can't whitelist by device address because of 2 layers of vdpa devices
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Rajesh Tailor
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-22 16:43 UTC by David Vallee Delisle
Modified: 2023-08-08 16:02 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NFV-2567 0 None None None 2022-07-15 14:06:57 UTC
Red Hat Issue Tracker OSP-10898 0 None None None 2021-11-22 16:48:58 UTC

Description David Vallee Delisle 2021-11-22 16:43:54 UTC 
Description of problem:

Because vdpa devices are 2 layers below the pf as opposed to one layer for standard sriov, the whitelist is not passing the devices.

Workaround:
sed -i 's/passthrough_whitelist={\"address\":\"06:00.[0-9]\",\"physical_network\"/passthrough_whitelist={\"physical_network\"/' /etc/nova/nova.conf

Version-Release number of selected component (if applicable):
master  branch
Comment 2 Bogdan Dobrelya 2022-07-15 14:01:02 UTC 
Unfortunately we no longer have expertise in the team for vDPA deployment automataion. I would defer that to NVF DFG.
Comment 5 Artom Lifshitz 2023-07-19 07:41:14 UTC 
Removing ga TM, effectively putting this in our backlog for 17.1.z for some value of z. This is not important enough to block/except anything.
Note You need to log in before you can comment on or make changes to this bug.