From 9ecabd0e2087cf0c47aabcb1c1f8c6c469187008 Mon Sep 17 00:00:00 2001 From: Suzana Fernandes Date: Thu, 8 May 2025 14:41:12 +0000 Subject: [PATCH] SRIOV VF interface will not be created on the system while host is locked (dsr10, r10) Change-Id: I1d8543aaf5c893fa2b4a3aec7939440e0c202c14 Signed-off-by: Suzana Fernandes --- .../provisioning-sr-iov-vf-interfaces-using-the-cli.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/source/node_management/kubernetes/node_interfaces/provisioning-sr-iov-vf-interfaces-using-the-cli.rst b/doc/source/node_management/kubernetes/node_interfaces/provisioning-sr-iov-vf-interfaces-using-the-cli.rst index 9755fbcae..5c09a46c3 100644 --- a/doc/source/node_management/kubernetes/node_interfaces/provisioning-sr-iov-vf-interfaces-using-the-cli.rst +++ b/doc/source/node_management/kubernetes/node_interfaces/provisioning-sr-iov-vf-interfaces-using-the-cli.rst @@ -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 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. For example: