From cef577401311e24b1b88fcc46f31e8fbbd99a894 Mon Sep 17 00:00:00 2001 From: Ashleigh Brennan Date: Tue, 20 Jan 2026 10:35:06 -0600 Subject: [PATCH] CNV-74970: Removing callouts from Support CNV docs modules --- modules/virt-configuring-pod-log-verbosity.adoc | 5 +++-- modules/virt-enable-guest-log-default-cli.adoc | 5 +++-- modules/virt-loki-log-queries.adoc | 10 ++++++---- modules/virt-set-guest-log-single-vm-cli.adoc | 5 +++-- virt/support/virt-troubleshooting.adoc | 2 +- 5 files changed, 16 insertions(+), 11 deletions(-) diff --git a/modules/virt-configuring-pod-log-verbosity.adoc b/modules/virt-configuring-pod-log-verbosity.adoc index f3c6c7ed9807..414a7d6e0dce 100644 --- a/modules/virt-configuring-pod-log-verbosity.adoc +++ b/modules/virt-configuring-pod-log-verbosity.adoc @@ -33,12 +33,13 @@ metadata: spec: logVerbosityConfig: kubevirt: - virtAPI: 5 <1> + virtAPI: 5 virtController: 4 virtHandler: 3 virtLauncher: 2 virtOperator: 6 ---- -<1> The log verbosity value must be an integer in the range `1–9`, where a higher number indicates a more detailed log. In this example, the `virtAPI` component logs are exposed if their priority level is `5` or higher. ++ +The log verbosity value must be an integer in the range `1–9`, where a higher number indicates a more detailed log. In this example, the `virtAPI` component logs are exposed if their priority level is `5` or higher. . Apply your changes by saving and exiting the editor. diff --git a/modules/virt-enable-guest-log-default-cli.adoc b/modules/virt-enable-guest-log-default-cli.adoc index 84219d900538..828b55dd38d7 100644 --- a/modules/virt-enable-guest-log-default-cli.adoc +++ b/modules/virt-enable-guest-log-default-cli.adoc @@ -31,7 +31,8 @@ metadata: name: kubevirt-hyperconverged spec: virtualMachineOptions: - disableSerialConsoleLog: true <1> + disableSerialConsoleLog: true #... ---- -<1> Set the value of `disableSerialConsoleLog` to `false` if you want serial console access to be enabled on VMs by default. ++ +Set the value of `disableSerialConsoleLog` to `false` if you want serial console access to be enabled on VMs by default. diff --git a/modules/virt-loki-log-queries.adoc b/modules/virt-loki-log-queries.adoc index ffb94d447d72..a4629aa60de9 100644 --- a/modules/virt-loki-log-queries.adoc +++ b/modules/virt-loki-log-queries.adoc @@ -83,10 +83,11 @@ If the query matches a large number of logs, the query might time out. |Container|[source,text] ---- -{log_type=~".+",kubernetes_container_name=~"\|"} <1> +{log_type=~".+",kubernetes_container_name=~"\|"} \|json\|kubernetes_labels_app_kubernetes_io_part_of="hyperconverged-cluster" ---- -<1> Specify one or more containers separated by a pipe (`\|`). + +Specify one or more containers separated by a pipe (`\|`). |`virt-launcher` |You must select *application* from the log type list before running this query. @@ -94,9 +95,10 @@ If the query matches a large number of logs, the query might time out. [source,text] ---- {log_type=~".+", kubernetes_container_name="compute"}\|json -\|!= "custom-ga-command" <1> +\|!= "custom-ga-command" ---- -<1> `\|!= "custom-ga-command"` excludes libvirt logs that contain the string `custom-ga-command`. (https://bugzilla.redhat.com/show_bug.cgi?id=2177684[*BZ#2177684*]) + +`\|!= "custom-ga-command"` excludes libvirt logs that contain the string `custom-ga-command`. (https://bugzilla.redhat.com/show_bug.cgi?id=2177684[*BZ#2177684*]) |==== You can filter log lines to include or exclude strings or regular expressions by using line filter expressions. diff --git a/modules/virt-set-guest-log-single-vm-cli.adoc b/modules/virt-set-guest-log-single-vm-cli.adoc index 8a5556604894..5a1624450a28 100644 --- a/modules/virt-set-guest-log-single-vm-cli.adoc +++ b/modules/virt-set-guest-log-single-vm-cli.adoc @@ -35,10 +35,11 @@ spec: spec: domain: devices: - logSerialConsole: true <1> + logSerialConsole: true #... ---- -<1> To enable access to the guest's serial console log, set the `logSerialConsole` value to `true`. ++ +To enable access to the guest's serial console log, set the `logSerialConsole` value to `true`. . Apply the new configuration to the VM by running the following command: + diff --git a/virt/support/virt-troubleshooting.adoc b/virt/support/virt-troubleshooting.adoc index 2fa25461dcab..700aafda30ca 100644 --- a/virt/support/virt-troubleshooting.adoc +++ b/virt/support/virt-troubleshooting.adoc @@ -51,7 +51,7 @@ include::modules/virt-viewing-logs-cli.adoc[leveloffset=+2] [id="guest-system-logs_{context}"] == Guest system logs -Viewing the boot logs of VM guests can help diagnose issues. You can configure access to guests' logs and view them by using either the {product-title} web console or the `oc` CLI. +Viewing the boot logs of VM guests can help diagnose issues. You can configure access to guests' logs and view them by using either the {product-title} web console or the {oc-first}. Even if the guest VM has no network, you can access it using its VNC or serial console, as documented in xref:../../virt/managing_vms/virt-accessing-vm-consoles.adoc#virt-accessing-vm-consoles[Connecting to virtual machine consoles]