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
PCI devices which are allocated to instances can be removed from the
[pci]device_spec configuration or can be removed from the hypervisor
directly. The existing PciTracker code handle this cases by keeping the
PciDevice in the nova DB exists and allocated and issue a warning in the
logs during the compute service startup that nova is in an inconsistent
state. Similar behavior is now added to the PCI placement tracking code
so the PCI inventories and allocations in placement is kept in such
situation.
There is one case where we cannot simply accept the PCI device
reconfiguration by keeping the existing allocations and applying the new
config. It is when a PF that is configured and allocated is removed and
VFs from this PF is now configured in the [pci]device_spec. And vice
versa when VFs are removed and its parent PF is configured. In this case
keeping the existing inventory and allocations and adding the new inventory
to placement would result in placement model where a single PCI device
would provide both PF and VF inventories. This dependent device
configuration is not supported as it could lead to double consumption.
In such situation the compute service will refuse to start.
blueprint: pci-device-tracking-in-placement
Change-Id: Id130893de650cc2d38953cea7cf9f53af71ced93
Copy file name to clipboardExpand all lines: doc/source/admin/pci-passthrough.rst
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -404,4 +404,20 @@ is upgraded. If there is an in-progress migration, then the PCI allocation on
404
404
the source host of the migration will not be healed. The placement view will be
405
405
consistent after such migration is completed or reverted.
406
406
407
+
Reconfiguring the PCI devices on the hypervisor or changing the
408
+
:oslo.config:option:`pci.device_spec` configuration option and restarting the
409
+
nova-compute service is supported in the following cases:
410
+
411
+
* new devices are added
412
+
* devices without allocation is removed
413
+
414
+
Removing a device that has allocations is not supported. If a device having any
415
+
allocation is removed then the nova-compute service will keep the device and
416
+
the allocation exists in the nova DB and in placement and logs a warning. If
417
+
a device with any allocation is reconfigured in a way that an allocated PF is
418
+
removed and VFs from the same PF is configured (or vice versa) then
419
+
nova-compute will refuse to start as it would create a situation where both
420
+
the PF and its VFs are made available for consumption.
421
+
422
+
407
423
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