-
Notifications
You must be signed in to change notification settings - Fork 111
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 firmware-level SRIOV enablement for e810-based NICs #438
Comments
@iancoolidge does the NIC in question (device ID) appear in [1] ? [1] https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/master/doc/supported-hardware.md |
Yes, each of Intel E810-CQDA2/2CQDA2 Family | 8086 | 1592 are supported and applicable here, and have a similar firmware control for enabling SRIOV |
Hi @iancoolidge for intel there is no need to configure anything in the firmware that I am aware of. please run |
@SchSeba lspci simply shows that the firmware-level setting is enabled, and one such setting does exist for e810-based cards. In the Mellanox case, prior to invocing For e810, on the servers that I am using, you can enable SRIOV through BIOS option, but maybe we need support from Intel to add this feature to their 'ethernet port configuration tool' or something. |
Hi @iancoolidge I don't think e810 as the same case as MLX cards. @Eoghan1232 can you please check this issue? |
Just catching up, the
As for SRIOV capability of the E800 series NICs, you would simply enable 2 BIOS settings:
Other than that, then the device is SRIOV capable, and requires no firmware configuration.
|
thanks @Eoghan1232 -- that BIOS configuration is exactly what I'm after here. With MLX, you can configure the NIC firmware in a system BIOS interface, or with the Are there any plans to expose this for e810 cards in a command line tool similarly? That would let |
Hi @iancoolidge I don't think the bios flag and the mstconfig doing the same thing... |
btw you can use something like redfish to do with an API but again that redfish API call will not be implemented as part of the operator. as must of the production deployments the out of band management port (what redfish will do the API call) is not connected to the workload/host network to avoid security issues. |
Can you please elaborate? |
yes, I agree that is not a good suggestion |
i believe @iancoolidge means there are some FW parameters exposed in UEFI and can be configured during node boot. |
no new comments closing this issue for housekeeping feel free you reopen if needed |
In the Mellanox plugin, if the CX6 firmware does not have VirtualizationMode=SRIOV and NumVFSAdvertised != 0, the mellanox glue code will call 'mstconfig' to set the firmware to enable SRIOV.
However, for the Intel e810 case, no such firmware settings management happens -- the SRIOV network operator just fails to detect SRIOV support.
The text was updated successfully, but these errors were encountered: