I have finished my testing with I210 NIC and the result shows that this way should be only used for SR-IOV physical function. And the blueprint "SR-IOV physical functions assignment with Neutron port" also indicates the same thing. https://blueprints.launchpad.net/nova/+spec/sriov-pf-passthrough-neutron-port
For this limitation, which way do you suggest?
1. Record as a known limitation and document how to pass through NICs which don't support SR-IOV. Like below: users need to override helm with PCI alias like following:
cat > nova-overrides.yaml <<EOF
conf:
nova:
DEFAULT:
debug: True
pci:
alias:
type: multistring
values:
- '{"vendor_id": "8086", "product_id": "37d2","device_type":"type-PCI","name": "pci-pass"}'
EOF
system helm-override-update stx-openstack nova openstack --values nova-overrides.yaml
2. Generate the helm override automatically. If this way is chosen, do you think this should be fixed in stx 2.0 or stx 3.0?
Hi Matt,
I have finished my testing with I210 NIC and the result shows that this way should be only used for SR-IOV physical function. And the blueprint "SR-IOV physical functions assignment with Neutron port" also indicates the same thing. /blueprints. launchpad. net/nova/ +spec/sriov- pf-passthrough- neutron- port
https:/
For this limitation, which way do you suggest? "device_ type":" type-PCI" ,"name" : "pci-pass"}' update stx-openstack nova openstack --values nova-overrides.yaml
1. Record as a known limitation and document how to pass through NICs which don't support SR-IOV. Like below: users need to override helm with PCI alias like following:
cat > nova-overrides.yaml <<EOF
conf:
nova:
DEFAULT:
debug: True
pci:
alias:
type: multistring
values:
- '{"vendor_id": "8086", "product_id": "37d2",
EOF
system helm-override-
2. Generate the helm override automatically. If this way is chosen, do you think this should be fixed in stx 2.0 or stx 3.0?