Bug 2070888 - Cannot bind driver vfio-pci when apply sriovnodenetworkpolicy with type vfio-pci
Summary: Cannot bind driver vfio-pci when apply sriovnodenetworkpolicy with type vfio-pci
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 4.11.0
Assignee: Balazs Nemeth
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On: 2068148
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-01 10:03 UTC by zhaozhanqi
Modified: 2022-10-13 08:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:03:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-network-operator pull 658 0 None open Bug 2070888: Use /run/ostree-booted to determine RHCOS 2022-05-03 14:52:59 UTC
Red Hat Bugzilla 2068148 1 medium CLOSED [4.11] /etc/redhat-release symlink is broken 2022-08-10 11:02:25 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:03:20 UTC

Description zhaozhanqi 2022-04-01 10:03:35 UTC 
Description of problem:

Met 'lastSyncError: Cannot bind driver vfio-pci to 0000:3b:0a.0, make sure IOMMU is enabled in BIOS' when apply policy on xxv710 card. 

Version-Release number of selected component (if applicable):
4.11.0-0.nightly-2022-03-29-152521

How reproducible:
always

Steps to Reproduce:
1. apply the following policy on card xxv710 card

apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
  name: intel-dpdk
  namespace: openshift-sriov-network-operator
spec:
  deviceType: vfio-pci
  mtu: 1700
  nicSelector:
    deviceID: "158b"
    pfNames:
      - ens1f1
    rootDevices:
      - '0000:3b:00.1'
    vendor: '8086'
  nodeSelector:
    feature.node.kubernetes.io/sriov-capable: 'true'
  numVfs: 2
  priority: 99
  resourceName: inteldpdk

2. show the following error when `oc get sriovnetworknodestates.sriovnetwork.openshift.io dell-per740-14.rhts.eng.pek2.redhat.com -o yaml `

    vendor: 15b3
  lastSyncError: Cannot bind driver vfio-pci to 0000:3b:0a.0, make sure IOMMU is enabled
    in BIOS
  syncStatus: InProgress


3. check ip link show vf1 all 00

# ip link show ens1f1
4: ens1f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1700 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 3c:fd:fe:ba:08:d5 brd ff:ff:ff:ff:ff:ff
    vf 0     link/ether 46:ac:9d:f4:99:3a brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off

4. check the dmesg

[ 3870.824044] iavf 0000:3b:0a.0: Multiqueue Enabled: Queue pair count = 4
[ 3870.831690] iavf 0000:3b:0a.0: MAC address: 46:ac:9d:f4:99:3a
[ 3870.837518] iavf 0000:3b:0a.0: GRO is enabled
[ 3870.842729] iavf 0000:3b:0a.0 ens1f1v0: renamed from eth0
[ 3870.862129] i40e 0000:3b:00.1: Setting MAC 46:ac:9d:f4:99:3a on VF 0
[ 3870.868669] iavf 0000:3b:0a.0: Reset warning received from the PF
[ 3870.874929] iavf 0000:3b:0a.0: Scheduling reset task
[ 3870.961779] i40e 0000:3b:00.1: Bring down and up the VF interface to make this change effective.
[ 3871.344634] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3871.413022] i40e 0000:3b:00.1: VF 0 in reset. Try again.
[ 3880.692774] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3889.917718] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3899.218367] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3908.446658] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3917.640292] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3926.936695] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3936.127721] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3945.325490] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3954.561777] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3963.761022] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3972.994797] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3982.174668] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 3991.384271] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4000.600431] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4009.786203] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4019.144563] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4028.377893] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4037.584291] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4046.763206] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4055.958972] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4065.163604] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4074.422660] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4083.689135] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4092.924836] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4102.098985] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4111.306890] vfio-pci: probe of 0000:3b:0a.0 failed with error -22
[ 4120.531267] vfio-pci: probe of 0000:3b:0a.0 failed with error -22

Actual results:


Expected results:


Additional info:
Comment 4 zhaozhanqi 2022-05-06 08:16:32 UTC 
Verified this bug on 4.11.0-202205051409
Comment 7 errata-xmlrpc 2022-08-10 11:03:06 UTC 
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.