From 1f15968f07f1ba383dfe7148bc66eac57fca3512 Mon Sep 17 00:00:00 2001 From: Amy Reyes Date: Mon, 25 Oct 2021 15:47:38 -0700 Subject: [PATCH] Updated per feedback Signed-off-by: Amy Reyes --- misc/debug_tools/acrn_log/README.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/misc/debug_tools/acrn_log/README.rst b/misc/debug_tools/acrn_log/README.rst index 7d3b5f259..1be4cfd13 100644 --- a/misc/debug_tools/acrn_log/README.rst +++ b/misc/debug_tools/acrn_log/README.rst @@ -52,7 +52,13 @@ steps: # acrnlog -n 8 -s 4 & You can use the ``loglevel`` command in the hypervisor shell (not the Service -VM shell) to query and change the hypervisor log level. +VM shell) to query or dynamically override the hypervisor log level +configuration settings made in the ACRN Configurator tool to the +:option:`hv.DEBUG_OPTIONS.MEM_LOGLEVEL`, +:option:`hv.DEBUG_OPTIONS.CONSOLE_LOGLEVEL`, and +:option:`hv.DEBUG_OPTIONS.NPK_LOGLEVEL` options. If the +system is rebooted, these log level settings will return to the +values set by the ACRN Configurator. The ``mem_loglevel`` parameter controls the log to be saved using ``acrnlog``, while the ``console_loglevel`` parameter controls the log