2
virt-top - 'top'-like utility for virtualization stats
8
virt-top is a top(1)-like utility for showing stats of virtualized
9
domains. Many keys and command line options are the same as for ordinary
12
It uses libvirt so it is capable of showing stats across a variety of
13
different virtualization systems.
16
-1 Display physical CPUs by default (instead of domains). When virt-top
17
is running, use the *1* key to toggle between physical CPUs and
20
-2 Display network interfaces by default (instead of domains). When
21
virt-top is running, use the *2* key to toggle between network
22
interfaces and domains display.
24
-3 Display block devices (virtual disks) by default (instead of
25
domains). When virt-top is running, use the *3* key to toggle
26
between block devices and domains display.
28
-b Batch mode. In this mode keypresses are ignored.
30
-c uri or --connect uri
31
Connect to the libvirt URI given.
33
To connect to QEMU/KVM you would normally do *-c qemu:///system*
35
To connect to Xen on the same host, do *-c xen:///*
37
To connect to libvirtd on a remote machine you would normally do *-c
40
If this option is not given then virt-top connects by default to
41
whatever is the default hypervisor for libvirt, although this can be
42
overridden by setting environment variables.
44
See the libvirt documentation at <http://libvirt.org/uri.html> for
48
Set the delay between screen updates in seconds. The default is 3.0
49
seconds. You can change this while virt-top is running by pressing
50
either *s* or *d* key.
53
Set the number of iterations to run. The default is to run
57
Set the sort order to one of: cpu (sort by %CPU used), mem (sort by
58
total memory), time (sort by total time), id (sort by domain ID),
59
name (sort by domain name), netrx (sort by network received bytes),
60
nettx (sort by network transmitted bytes), blockrdrq (sort by block
61
device [disk] read requests), blockwrrq (sort by block device [disk]
64
While virt-top is running you can change the sort order using keys
65
*P* (cpu), *M* (memory), *T* (total time), *N* (domain ID), *F*
66
(interactively select the sort field).
68
-s Secure mode. Currently this does nothing.
71
Set the time in seconds between updates of the historical %CPU at
72
the top right of the display.
75
Write the statistics to file *file.csv*. First a header is written
76
showing the statistics being recorded in each column, then one line
77
is written for each screen update. The CSV file can be loaded
78
directly by most spreadsheet programs.
80
Currently the statistics which this records vary between releases of
81
virt-top (but the column headers will stay the same, so you can use
82
those to process the CSV file).
84
Not every version of virt-top supports CSV output - it depends how
85
the program was compiled (see *README* file in the source
86
distribution for details).
88
To save space you can compress your CSV files (if your shell
89
supports this feature, eg. *bash*):
91
virt-top --csv >(gzip -9 > output.csv.gz)
93
You can use a similar trick to split the CSV file up. In this
94
example the CSV file is split every 1000 lines into files called
95
*output.csv.00*, *output.csv.01* etc.
97
virt-top --csv >(split -d -l 1000 - output.csv.)
100
Disable domain CPU stats in CSV output.
103
Disable domain memory stats in CSV output.
106
Disable domain block device stats in CSV output.
109
Disable domain network interface stats in CSV output.
112
Send debug and error messages to *filename*. To send error messages
113
to syslog you can do:
115
virt-top --debug >(logger -t virt-top)
117
See also REPORTING BUGS below.
120
Read *filename* as the init file instead of the default which is
121
*$HOME/.virt-toprc*. See also INIT FILE below.
124
Do not read any init file.
127
Script mode. There will be no user interface. This is most useful
128
when used together with the *--csv* and *-n* options.
131
Stream mode. All output is sent to stdout. This can be used from
132
shell scripts etc. There is no user interface.
135
Show I/O statistics in Bytes. Default is shown in the number of
139
The program will exit at the *time* given.
141
The time may be given in one of the following formats:
143
*YYYY-MM-DD HH:MM:SS*
144
End time is the date and time given.
147
End time is the time given, today.
150
End time is HH hours, MM minutes, SS seconds in the future
151
(counted from the moment that program starts).
154
End time is *secs* seconds in the future.
156
For example to run the program for 3 minutes you could do:
158
virt-top --end-time +00:03:00
162
virt-top --end-time +180
164
Not every version of virt-top supports this option - it depends how
165
the program was compiled (see *README* file in the source
166
distribution for details).
169
Display usage summary.
172
Display version number and exit.
175
Note that keys are case sensitive. For example use upper-case *P* (shift
176
P) to sort by %CPU. *^* before a key means a Ctrl key, so *^L* is Ctrl
182
*q* Quits the program.
187
Change the delay between screen updates.
189
*B* Toggle Block I/O statistics so they are shown in either bytes or
193
Show the normal list of domains display.
196
Toggle into showing physical CPUs. If pressed again toggles back to
197
showing domains (the normal display).
199
*2* Toggle into showing network interfaces. If pressed again toggles
200
back to showing domains.
202
*3* Toggle into showing block devices (virtual disks). If pressed again
203
toggles back to showing domains.
207
*M* Sort by total memory. Note that this shows the total memory
208
allocated to the guest, not the memory being used.
210
*T* Sort by total time.
212
*N* Sort by domain ID.
214
*F* Select the sort field interactively (there are other sort fields you
215
can choose using this key).
217
*W* This creates or overwrites the init file with the current settings.
219
This key is disabled if *--no-init-file* was specified on the
220
command line or if *overwrite-init-file false* is given in the init
224
When virt-top starts up, it reads initial settings from the file
225
*.virt-toprc* in the user's home directory.
227
The name of this file may be overridden using the *--init-file filename*
228
command line option or may be disabled entirely using *--no-init-file*.
230
The init file has a simple format. Blank lines and comments beginning
231
with *#* are ignored. Everything else is a set of *key value* pairs,
234
display *task|pcpu|block|net*
235
Sets the major display mode to one of *task* (tasks, the default),
236
*pcpu* (physical CPUs), *block* (block devices), or *net* (network
240
Sets the delay between display updates in seconds.
243
Sets the historical CPU delay in seconds.
246
Sets the number of iterations to run before we exit. Setting this to
247
*-1* means to run continuously.
249
sort *cpu|mem|time|id|name|...*
250
Sets the sort order. The option names are the same as for the
251
command line *-o* option.
254
Sets the default connection URI.
257
Sets the default filename to use for debug and error messages.
260
Enables CSV output to the named file.
263
Enable or disable domain CPU stats in CSV output.
266
Enable or disable domain memory stats in CSV output.
268
csv-block *true|false*
269
Enable or disable domain block device stats in CSV output.
272
Enable or disable domain network interface stats in CSV output.
286
block-in-bytes *true|false*
287
Show block device statistics in bytes.
290
Set the time at which the program exits. See above for the time
293
overwrite-init-file *false*
294
If set to *false* then the *W* key will not overwrite the init file.
296
Note that in the current implementation, options specified in the init
297
file override options specified on the command line. This is a bug and
298
this behaviour may change in the future.
302
This I/O value is the amount of I/O since the previous iteration of
303
virt-top. To calculate speed of I/O, you should divide the number by
306
NETWORK RX BYTES AND PACKETS
307
Libvirt/virt-top has no way to know that a packet transmitted to a guest
308
was received (eg. if the guest is not listening). In the network RX
309
stats, virt-top reports the packets transmitted to the guest, on the
310
basis that the guest might receive them.
312
In particular this includes broadcast packets. Because of the way that
313
Linux bridges work, if the guest is connected to a bridge, it will
314
probably see a steady "background noise" of RX packets even when the
315
network interface is idle or down. These are caused by STP packets
316
generated by the bridge.
318
DEBUGGING LIBVIRT ISSUES
319
virt-top tries to turn libvirt errors into informative messages. However
320
if libvirt initialization fails then this is not possible. Instead you
321
will get an obscure error like:
323
libvir: error : Unknown failure
324
Fatal error: exception Libvirt.Virterror(...)
326
To see the cause of libvirt errors in more detail, enable libvirt
327
debugging by setting this environment variable:
329
export LIBVIRT_DEBUG=1
332
top(1), virsh(1), <http://www.libvirt.org/ocaml/>,
333
<http://www.libvirt.org/>, <http://people.redhat.com/~rjones/>,
334
<http://caml.inria.fr/>
337
Richard W.M. Jones <rjones @ redhat . com>
340
(C) Copyright 2007-2011 Red Hat Inc., Richard W.M. Jones
343
This program is free software; you can redistribute it and/or modify it
344
under the terms of the GNU General Public License as published by the
345
Free Software Foundation; either version 2 of the License, or (at your
346
option) any later version.
348
This program is distributed in the hope that it will be useful, but
349
WITHOUT ANY WARRANTY; without even the implied warranty of
350
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
351
Public License for more details.
353
You should have received a copy of the GNU General Public License along
354
with this program; if not, write to the Free Software Foundation, Inc.,
355
675 Mass Ave, Cambridge, MA 02139, USA.
358
Bugs can be viewed on the Red Hat Bugzilla page:
359
<https://bugzilla.redhat.com/>.
361
If you find a bug in virt-top, please follow these steps to report it:
363
1. Check for existing bug reports
364
Go to <https://bugzilla.redhat.com/> and search for similar bugs.
365
Someone may already have reported the same bug, and they may even
368
2. Capture debug and error messages
371
virt-top --debug virt-top.log
373
and keep *virt-top.log*. It contains error messages which you should
374
submit with your bug report.
376
3. Get version of virt-top and version of libvirt.
381
If you can get the precise version of libvirt you are using then
384
4. Submit a bug report.
385
Go to <https://bugzilla.redhat.com/> and enter a new bug. Please
386
describe the problem in as much detail as possible.
388
Remember to include the version numbers (step 3) and the debug
389
messages file (step 2).
391
5. Assign the bug to rjones @ redhat.com
392
Assign or reassign the bug to rjones @ redhat.com (without the
393
spaces). You can also send me an email with the bug number if you
394
want a faster response.