shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-03-20 06:50:22 +03:00
Code Releases Activity

docs: fix 'virsh domstats --vcpu' measure units and descriptions

Browse Source 
The fields are in nanoseconds, not microseconds. Also fixes the
description of `vcpu.<num>.wait`, as it does not actually represent the
time waiting on I/O.

Signed-off-by: Fabricio Duarte <fabricio.duarte.jr@gmail.com>
Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
This commit is contained in:
Fabricio Duarte 2024-12-16 19:02:44 -03:00 committed by Martin Kletzander
parent 4589468c69
commit 0d9d439175
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/manpages/virsh.rst
View File

@ -2434,14 +2434,15 @@ When selecting the *--state* group the following fields are returned:
* ``vcpu.<num>.state`` - state of the virtual CPU <num>, as
number from virVcpuState enum
* ``vcpu.<num>.time`` - virtual cpu time spent by virtual
CPU <num> (in microseconds)
* ``vcpu.<num>.wait`` - virtual cpu time spent by virtual
CPU <num> waiting on I/O (in microseconds)
CPU <num> (in nanoseconds)
* ``vcpu.<num>.wait`` - time the vCPU <num> 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.<num>.halted`` - virtual CPU <num> is halted: yes or
no (may indicate the processor is idle or even disabled,
depending on the architecture)
* ``vcpu.<num>.delay`` - time the vCPU <num> thread was enqueued by the
host scheduler, but was waiting in the queue instead of running (in nanoseconds).
* ``vcpu.<num>.delay`` - time the vCPU <num> 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