Skip to content

CNV- 45694: Added documentation for kubevirt_vmi_vcpu_delay_seconds_total #96063

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
wants to merge 1 commit into
base: enterprise-4.20
Choose a base branch
from
Open

CNV- 45694: Added documentation for kubevirt_vmi_vcpu_delay_seconds_total #96063

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
9 changes: 9 additions & 0 deletions modules/virt-querying-metrics.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,15 @@ A value above '0' means that the vCPU wants to run, but the host scheduler canno
====
To query the vCPU metric, the `schedstats=enable` kernel argument must first be applied to the `MachineConfig` object. This kernel argument enables scheduler statistics used for debugging and performance tuning and adds a minor additional load to the scheduler.
====
The `kubevirt_vmi_vcpu_delay_seconds_total` metric reports the cumulative time that a vCPU was enqueued by the host scheduler but could not run immediately. This delay is exposed to the virtual machine (VM) as steal time and can affect performance, often indicating CPU overcommitment or contention on the host.

.Example vCPU delay query
[source,PromQL]
----
irate(kubevirt_vmi_vcpu_delay_seconds_total[5m]) > 0.05
----

This query returns the average per-second delay over a 5-minute period. A high value may indicate CPU overcommitment or contention on the node.

.Example vCPU wait time query
[source,promql]
Expand Down