Skip to content

Sync CNV runbook GuestVCPUQueueHighWarning.md (Updated at 2026-02-03 12:16:09 +0000 UTC) #392

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hco-bot wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Sync CNV runbook GuestVCPUQueueHighWarning.md (Updated at 2026-02-03 12:16:09 +0000 UTC) #392

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions alerts/openshift-virtualization-operator/GuestVCPUQueueHighWarning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ uninterruptible threads. The run‑queue length is derived from

## Impact

* Moderate CPU contention inside the guest. Latency may spike but workload still
* Moderate CPU contention inside the guest VM. Latency might spike but workload still
progresses.

* An early signal that the VM might need additional vCPUs or that a short‑lived
Expand All @@ -32,19 +32,19 @@ process is causing bursts.

4. **Verify vCPU allocation**
```bash
oc get vmi $VM -ojsonpath='{.spec.domain.cpu}'
$ oc get vmi $VM -ojsonpath='{.spec.domain.cpu}'
```

## Mitigation

* **Immediately:** Consider live-migrating the VM to a node under a lighter
load,
or throttle demanding processes.
* **Short term:** Hot-plug or increase vCPU limit; tune application thread
* **Short term:** Hot plug or increase vCPU limit; tune application thread
pools.
* **Long term:** Implement horizontal scaling (HPA/KEDA, VMReplicaSet);
review placement rules.

If you cannot resolve the issue, log in to the
[Customer Portal](https://access.redhat.com) and open a support case,
[Red Hat Customer Portal](https://access.redhat.com) and open a support case,
attaching the artifacts gathered during the diagnosis procedure.