From 0d9d439175990f1a75bad002d4799df6ac9f4805 Mon Sep 17 00:00:00 2001 From: Fabricio Duarte Date: Mon, 16 Dec 2024 19:02:44 -0300 Subject: [PATCH] docs: fix 'virsh domstats --vcpu' measure units and descriptions The fields are in nanoseconds, not microseconds. Also fixes the description of `vcpu..wait`, as it does not actually represent the time waiting on I/O. Signed-off-by: Fabricio Duarte Reviewed-by: Martin Kletzander --- docs/manpages/virsh.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/manpages/virsh.rst b/docs/manpages/virsh.rst index 868b354b2f..cbec1b8ef4 100644 --- a/docs/manpages/virsh.rst +++ b/docs/manpages/virsh.rst @@ -2434,14 +2434,15 @@ When selecting the *--state* group the following fields are returned: * ``vcpu..state`` - state of the virtual CPU , as number from virVcpuState enum * ``vcpu..time`` - virtual cpu time spent by virtual - CPU (in microseconds) -* ``vcpu..wait`` - virtual cpu time spent by virtual - CPU waiting on I/O (in microseconds) + CPU (in nanoseconds) +* ``vcpu..wait`` - time the vCPU thread was waiting in the runqueue + as the scheduler has something else running ahead of it (in nanoseconds), + requires CONFIG_SCHED_INFO on Linux * ``vcpu..halted`` - virtual CPU is halted: yes or no (may indicate the processor is idle or even disabled, depending on the architecture) -* ``vcpu..delay`` - time the vCPU thread was enqueued by the - host scheduler, but was waiting in the queue instead of running (in nanoseconds). +* ``vcpu..delay`` - time the vCPU thread was waiting in the runqueue + as the scheduler has something else running ahead of it (in nanoseconds). Exposed to the VM as a steal time. This group of statistics also reports additional hypervisor-originating per-vCPU -- 2.47.3