Bug 2025649

Summary: [vDPA] can't whitelist by device address because of 2 layers of vdpa devices
Product: Red Hat OpenStack Reporter: David Vallee Delisle <dvd>
Component: openstack-novaAssignee: Rajesh Tailor <ratailor>
Status: NEW --- QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: alifshit, bdobreli, dasmith, eglynn, jhakimra, kchamart, ratailor, sbauza, sgordon, vromanso
Target Milestone: ---Keywords: Triaged
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: 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 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.