-
Notifications
You must be signed in to change notification settings - Fork 114
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
Request support for E823-C NICs which are used in Kontron ME1310 servers #501
Comments
Hi @murali509, if you need you can update the configmap when you deploy the operator. on that PR please show a case where a pod is able to use the netdevice and also user-space for a dpdk application. |
I tried to update the configmap by appending below line and restarted sriov related pods: Intel_ice_Columbiapark_E823C: "8086 188a" I observed that sriov-network-config-daemon-qw9s4 pod is failing to start with below error in the logs: kubectl logs sriov-network-config-daemon-qw9s4 -n gke-operators goroutine 1 [running]: Any help on fixing this issue is highly appreciated. Thank you. |
Hi, |
Oh yeah, I missed to provide 3rd value in the config map. Thanks for quick fix. |
Issue is resolved after adding the E823-C NIC in the config map as mentioned in the PR #520: I have tested binding the VFs to a DPDK driver as you can see the output for eno2 NIC (E823C) below with vfio-pci type: kubectl -n gke-operators get SriovNetworkNodeState dauk-mrl-k-gdcv-host02.denseair.net -o yaml apiVersion: sriovnetwork.k8s.cni.cncf.io/v1 |
We are using Kontron ME1310 Servers for deploying GDCv clusters. Upon checking, we observed that we are unable to create VFs due to unavailability of support for E823-C NICs as seen in the configmap https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/master/deploy/configmap.yaml
Request you to add support for E823-C NICs.
The text was updated successfully, but these errors were encountered: