-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No SRIOV devices available #609
Comments
Can you try "rootDevices" instead of "pciAddresses". |
@rollandf I tried using the pfNames as follows
As a test I added both vfio and mlx5_core as drivers under the VF , all the VF on one phy interface are vfio bound the other are still mlx5_core. Even with that I still don't get any devices. |
Just a quick follow up , when I remove the pfNames , I then see the resources being populated.
Is it something in match pattern , you can see from the attached logs and output that the pfNames seem to be correct. |
@rollandf any idea why when I use the patterns here #609 (comment) that it won't discover the devices ? |
I would try without the 'vf' for NVIDIA NICs:
|
@gavmckee80 can we close this issue? |
What happened?
Resources failed to be discovered on a node
Logs from the sriov plugin
What did you expect to happen?
I expected to be able to see mlnx_sriov_cx7 resources available
What are the minimal steps needed to reproduce the bug?
I suspect that the issue relates to this line in the log
Anything else we need to know?
I am using tuned to isolate CPU cores
Component Versions
Please fill in the below table with the version numbers of components used.
Config Files
Config file locations may be config dependent.
Device pool config file location (Try '/etc/pcidp/config.json')
Multus config (Try '/etc/cni/multus/net.d')
CNI config (Try '/etc/cni/net.d/')
Kubernetes deployment type ( Bare Metal, Kubeadm etc.)
Kubeconfig file
SR-IOV Network Custom Resource Definition
Logs
SR-IOV Network Device Plugin Logs (use
kubectl logs $PODNAME
)Multus logs (If enabled. Try '/var/log/multus.log' )
Kubelet logs (journalctl -u kubelet)
The text was updated successfully, but these errors were encountered: