Open seb-835 opened 2 years ago
Hi @e0ne @seb-835 any update on this issue or we can close it?
No update on this case, still having the issue. Any help appreciate to soldve it.
Greeting!
After node sriov configuration via config daemon and before scheduling an IB workload on the node what are the VFs hardware address ?
it seems they are all zeroes or ones according to CNI failure
what OS and kernel are you using ? maybe the kernel does not support get/set of VF port and node guid
in sriov-network-config-daemon logs do you see error after: : "setVfGuid()" log msg ?
can you add sriov-network-config-daemon logs when it tries to configure sriov for the node ?
I also have the same problem, I don't know how to solve it, does anyone know how to solve it, please contact me, my email is fu7100@gmail.com
Hi @seb-835 @fu7100 any update on this issue we are waiting for some logs. If you manage to make it work let me know I will close this issue thanks!
I have the same question. "infiniBand SRI-OV CNI failed to configure VF "VF ib9 GUID is not valid""。 I solved this problem by manually configuring the node, port and policy of VF. However, I am puzzled that the plug-in should automatically configure the relevant information of VF, instead of requiring me to configure it manually. What is the reason for this? Can you help me solve it? Thank you very much.
I have the same question. "infiniBand SRI-OV CNI failed to configure VF "VF ib9 GUID is not valid""。 I solved this problem by manually configuring the node, port and policy of VF. However, I am puzzled that the plug-in should automatically configure the relevant information of VF, instead of requiring me to configure it manually. What is the reason for this? Can you help me solve it? Thank you very much.
Hi @frye233
Could you tell me how did you manually configure the node/port GUID of VF? I have the same issue with raw ib-sriov cni and dp deployment. In addition, the VF I created all remain DOWN and I don't know how to bring them up though the ib PF is UP. thanks.
any update on this issue or we can close it?
Hi Team,
i think i am really near to get it work, but got this in describing my testing pod:
i use the following manifest to test :
can you give me advice to fix it ? Thanks a lot