You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Either the vendor_id and product_id needs to be set or the
resource_class needs to be set in each alias. This is now validated when
the alias is parsed to avoid late failure during placement
allocation_candidates query.
Conflicts:
nova/conf/pci.py due to I62ec475988eab8de948498f50d8d4c0d47321102
not on stable/2025.1
Closes-Bug: #2111440
Change-Id: I7fd43b3d6faac8c4098b0983e8adc596414823a1
(cherry picked from commit acc6221)
Copy file name to clipboardExpand all lines: doc/source/admin/pci-passthrough.rst
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -494,7 +494,9 @@ configuration option supports requesting devices by Placement resource class
494
494
name via the ``resource_class`` field and also support requesting traits to
495
495
be present on the selected devices via the ``traits`` field in the alias. If
496
496
the ``resource_class`` field is not specified in the alias then it is defaulted
497
-
by nova to ``CUSTOM_PCI_<vendor_id>_<product_id>``.
497
+
by nova to ``CUSTOM_PCI_<vendor_id>_<product_id>``. Either the ``product_id``
498
+
and ``vendor_id`` or the ``resource_class`` field must be provided in each
499
+
alias.
498
500
499
501
For deeper technical details please read the `nova specification. <https://specs.openstack.org/openstack/nova-specs/specs/zed/approved/pci-device-tracking-in-placement.html>`_
0 commit comments