Intel VF attached to VM might not be recognized

[ccristian123]

Hi,

If an Intel XXV710 rev.2 VF is attached to openshift vm worker it will be presented in PCI space of VM as 8086:154c. However the 154c does not pass validation since it's not in device ids supported map ( ids[1] in deploy/configmap.yaml). This happens for RHOSP16.1 and OCP4.8.

Br,
Cristian

[zshi-redhat]

@ccristian123 What are the PF and VF device IDs for Intel XXV710 rev2?

I noticed there is this ID in the configmap: https://github.com/openshift/sriov-network-operator/blob/master/deploy/configmap.yaml#L6

[ccristian123]

PF assuming is the vendor_model_id in [vendor_id:vendor_model_id] is 154c; does not mach id[1] in any of the entries. How do you find the VF?

[zshi-redhat]

@ccristian123 I see your point, this is a bug when sriov operator is used in VMs (where PF doesn't exist in VM).
We are working on a fix for this issue.

[openshift-bot]

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

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.