Comments (9)
I do not understand why It try to get VF information from other NIC which is not I configured.
* Configured NIC : 0000:04:00.0 * Try to get from : 0000:05:00.1
0000:04:00.0
is the PF pci address.
The error message is from sriov-cni, it tries to get the PF interface name from 0000:05:00.1
device.
This 0000:05:00.1
pci address should come from kubelet which allocates the available VF device and eventually pass it down to sriov-cni.
Also one more thing is that I could not see "intel.com/intel-nics" when I execute command below:
$ kubectl get no -o json | jq -r '[.items[] | {name:.metadata.name, allocable:.status.allocatable}]'
you have the resource name defined as testsriov01
in the sriov node policy, so the openshift.io/testsriov01
is the resource name you should be looking for. it reports 9 available VF devices.
Do anyone have experience about this?
It looks like you have a mismatch between sriov node policy (numvfs: 2) and the actual reported device (9), there might be something wrong with vf provisioning. could you check how many vf devices are created on the worker node?
from sriov-network-operator.
Thanks for quick answer.
On the worker node, the 2 VFs were created as:
It seems something wrong during vf provisioning as you mentioned.
Actually, the way I deploy sriov-network-operator was clone from this git and build manually, not followed official document. (Because it does not work on my cluster)
Could this be reasons why error occurred?
from sriov-network-operator.
could you share the output of oc get configmap -n openshift-sriov-network-operator device-plugin-config -o yaml
?
the namespace might be sriov-network-operator
if you deployed the operator on vanilla k8s environment.
Also could you check which PF this device 0000:05:00.1
belongs to?
from sriov-network-operator.
Here is the output of oc get configmap -n openshift-sriov-network-operator device-plugin-config -o yaml
.
The device 0000:05:00.1
is Physical Interface(PF), not a VF.
from sriov-network-operator.
Here is the output of
oc get configmap -n openshift-sriov-network-operator device-plugin-config -o yaml
.The device
0000:05:00.1
is Physical Interface(PF), not a VF.
Ok, I think the issue is with above device plugin config map, it groups all the devices with same vendor IDs (8086) as a resource pool. so when you create a pod requesting device from that pool, it randomly chooses one (which happened to be the PF interface 0000:05:00.1
), then sriov-cni failed to find PF name of that PF interface because sriov-cni only supports attaching VF device to pod.
You could try specify the pfNames
in the sriov network node policy with the pf name of 0000:04:00.0
device.
Once the policy is successfully applied and the resource number is refreshed in node status, then re-creating the pod shall work as expected.
from sriov-network-operator.
I added pfName
parameter on policy yaml file and re-create pod, then it successfully executed well.
Thank you for help.
However, I also test to attach the SRIOV on KubeVirt
vmi. But it seems not work on KubeVirt
.
Is there something more that I have to configure for KubeVirt
?
from sriov-network-operator.
I added
pfName
parameter on policy yaml file and re-create pod, then it successfully executed well.
Thank you for help.However, I also test to attach the SRIOV on
KubeVirt
vmi. But it seems not work onKubeVirt
.
Is there something more that I have to configure forKubeVirt
?
Comparing with what I tested, one difference is in the interfaces section: where I was using sriov, while above template uses bridge, not sure if that matters.
from sriov-network-operator.
Hi @rupang790 please take a look on the kubevirt sriov documentation https://kubevirt.io/user-guide/#/creation/interfaces-and-networks?id=sriov
from sriov-network-operator.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from sriov-network-operator.
Related Issues (20)
- Inability to read current configuration values from ConnectX-3 EN NICs causes panic HOT 5
- Support for Mellanox connectX6 Lx cards - missing documentation? HOT 2
- network-resources-injector and operator-webhook daemonset should have configurable tolerations HOT 4
- Cannot config Mellanox ConnectX-4 Lx on CoreOS HOT 9
- FEC operator needs the SNO leadership election optimizations that were done for all other components, sriov operator HOT 3
- [Bugs] DeviceID in sriov-device-plugin is different from the one in SRIOV Net Policy HOT 7
- Can not work well with Intel x710 HOT 7
- sriovnetworknodestates is not detecting sriov VF's HOT 7
- Does sriov-network-operator support arm? HOT 4
- In ovs-offload mode, vf and vf rep interfaces cannot be created HOT 3
- No firmware-level SRIOV enablement for e810-based NICs
- Pod schedule failure when restarting device plugin HOT 10
- Worker="" vs Worker="foo" HOT 6
- How to configure the same policy for different nics configurations of different nodes HOT 2
- master and release-4.16 still point to 4.15 versions HOT 9
- Openshift is configured with the sriov network card, but the network card cannot be seen in the pod. But it can be seen in the yaml configuration HOT 3
- No SetVfGuid() HOT 3
- sriov-network-operator is not up by error "unable to create index fieldn version \"sriovnetwork.openshift.io/v1\""}" HOT 4
- Can't parse image name - not authorized HOT 2
- which repo to use HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sriov-network-operator.