starlingx/docs
Code Issues Proposed changes

SRIOV VF interface will not be created on the system while host is locked (dsr10, r10)

Browse Source 
Change-Id: I1d8543aaf5c893fa2b4a3aec7939440e0c202c14
Signed-off-by: Suzana Fernandes <Suzana.Fernandes@windriver.com>
(cherry picked from commit 9ecabd0e2087cf0c47aabcb1c1f8c6c469187008)
This commit is contained in:
Suzana Fernandes 2025-05-08 14:41:12 +00:00 committed by Suzana Barude Fernandes
parent 720d8f1ddb
commit 0b4fd1c8eb
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/node_management/kubernetes/node_interfaces/provisioning-sr-iov-vf-interfaces-using-the-cli.rst
View File

@ -45,6 +45,14 @@ For more information, see :ref:`Provision SR-IOV Interfaces using the CLI
|AIO-SX| hosts do not need to be locked to provision an |SRIOV| interface and |AIO-SX| hosts do not need to be locked to provision an |SRIOV| interface and
assign it to a data network. assign it to a data network.
.. note::
When a host is locked, newly created |SRIOV| |VF| or modifications to
existing VFs are not applied on the system, only the database is
updated. As a result, any network using newly created VFs (PODs)
will not be operational until the host is unlocked and the changes are
applied. However, existing VFs will continue to work with the
current configuration even with pending modifications.
#. Identify the parent |SRIOV| interface to be configured. #. Identify the parent |SRIOV| interface to be configured.
For example: For example: