From 4313dbcc96fbb4d3987be6dda1f533744507f8fe Mon Sep 17 00:00:00 2001
From: hco-bot <71450783+hco-bot@users.noreply.github.com>
Date: Tue, 16 Sep 2025 04:36:04 +0000
Subject: [PATCH] Sync CNV runbook KubeVirtVMGuestMemoryPressure.md (Updated at
 2025-09-15 08:41:07 +0000 UTC)

---
 .../KubeVirtVMGuestMemoryPressure.md          | 69 +++++++++++++++++++
 1 file changed, 69 insertions(+)
 create mode 100644 alerts/openshift-virtualization-operator/KubeVirtVMGuestMemoryPressure.md

diff --git a/alerts/openshift-virtualization-operator/KubeVirtVMGuestMemoryPressure.md b/alerts/openshift-virtualization-operator/KubeVirtVMGuestMemoryPressure.md
new file mode 100644
index 00000000..b7caebba
--- /dev/null
+++ b/alerts/openshift-virtualization-operator/KubeVirtVMGuestMemoryPressure.md
@@ -0,0 +1,69 @@
+# KubeVirtVMGuestMemoryPressure
+
+## Meaning
+The VM guest OS is under sustained memory pressure (low usable memory
+with elevated major page faults and/or swap I/O), risking thrashing,
+swapping, or OOM kills.
+
+## Impact
+- Performance degradation due to page thrashing
+- Increased swap I/O and latency
+- Risk of OOM kills and application instability
+
+## Diagnosis
+- Metrics (Prometheus)
+  1) Identify the VMI pod (`vmi_pod` label):
+  ```promql
+  kubevirt_vmi_info{vm="<vm-name>", namespace="<namespace>",
+  phase="running"}
+  ```
+  2) Headroom (usable/available) < 5% indicates pressure:
+  ```promql
+  sum by (name, namespace) (
+    kubevirt_vmi_memory_usable_bytes{
+      name="<vmi_pod>", namespace="<namespace>"
+    }
+  ) /
+  sum by (name, namespace) (
+    kubevirt_vmi_memory_available_bytes{
+      name="<vmi_pod>", namespace="<namespace>"
+    }
+  )
+  ```
+  3) Major page faults are elevated:
+  ```promql
+  sum by (name, namespace) (
+    rate(
+      kubevirt_vmi_memory_pgmajfault_total{
+        name="<vmi_pod>", namespace="<namespace>"
+      }[5m]
+    )
+  )
+  ```
+  4) Swap traffic is elevated (bytes/s):
+  ```promql
+  sum by (name, namespace) (
+    rate(
+      kubevirt_vmi_memory_swap_in_traffic_bytes{
+        name="<vmi_pod>", namespace="<namespace>"
+      }[5m]
+    ) +
+    rate(
+      kubevirt_vmi_memory_swap_out_traffic_bytes{
+        name="<vmi_pod>", namespace="<namespace>"
+      }[5m]
+    )
+  )
+  ```
+
+## Mitigation
+- Short term (in guest)
+  - If possible, Restart or tune memory-heavy processes; reduce workload.
+  - If acceptable, drop caches temporarily.
+  - Ensure swap is sized/policy-compliant (or disabled if not desired).
+
+- Increase VM memory (hotplug if supported; otherwise restart may be required)
+
+If you cannot resolve the issue, log in to the
+[Customer Portal](https://access.redhat.com) and open a support case,
+attaching the artifacts gathered during the diagnosis procedure.
\ No newline at end of file