Hi Michal,
Seems there is a typo of 'restrictive' instead of 'strict' in the last line of updated content. Right?
Best Regards,
Jing Qi
On Fri, Dec 17, 2021 at 12:02 AM Michal Privoznik <mprivozn@xxxxxxxxxx> wrote:
While we document possibility of passing an integer from
virDomainNumatuneMemMode enum, we list string variants to only
the first three enum members. The fourth (and so far the last)
member is called 'restrictive' and thus should be documented.
Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>
---
docs/manpages/virsh.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/manpages/virsh.rst b/docs/manpages/virsh.rst
index 611a6271cf..cd739c32c4 100644
--- a/docs/manpages/virsh.rst
+++ b/docs/manpages/virsh.rst
@@ -3545,11 +3545,11 @@ Set or get a domain's numa parameters, corresponding to the <numatune>
element of domain XML. Without flags, the current settings are
displayed.
-*mode* can be one of \`strict', \`interleave' and \`preferred' or any
-valid number from the virDomainNumatuneMemMode enum in case the daemon
-supports it. For a running domain, the mode can't be changed, and the
-nodeset can be changed only if the domain was started with a mode of
-\`strict'.
+*mode* can be one of \`strict', \`interleave', \`preferred' and
+\'restrictive' or any valid number from the virDomainNumatuneMemMode enum
+in case the daemon supports it. For a running domain, the mode can't be
+changed, and the nodeset can be changed only if the domain was started with
+a mode of \`strict'.
*nodeset* is a list of numa nodes used by the host for running the domain.
Its syntax is a comma separated list, with '-' for ranges and '^' for
--
2.32.0
Thanks & Regards,
Jing,Qi
Jing,Qi
