Connect to URI given. The default is to connect to the Xen
hypervisor.
+ To connect to QEMU/KVM you would normally do *-c qemu:///system*
+
+ To connect to libvirtd on a remote machine you would normally do *-c
+ xen://host/*
+
+ Full details on connection URIs is available at
+ <http://libvirt.org/uri.html>
+
-d delay
Set the delay between screen updates in seconds. The default is 3.0
seconds. You can change this while virt-top is running by pressing
-o sort
Set the sort order to one of: cpu (sort by %CPU used), mem (sort by
- memory used), time (sort by total time), id (sort by domain ID),
+ total memory), time (sort by total time), id (sort by domain ID),
name (sort by domain name), netrx (sort by network received bytes),
nettx (sort by network transmitted bytes), blockrdrq (sort by block
device [disk] read requests), blockwrrq (sort by block device [disk]
Script mode. There will be no user interface. This is most useful
when used together with the *--csv* and *-n* options.
+ --stream
+ Stream mode. All output is sent to stdout. This can be used from
+ shell scripts etc. There is no user interface.
+
+ --block-in-bytes
+ Show I/O statistics in Bytes. Default is shown in the number of
+ Requests.
+
--end-time time
The program will exit at the *time* given.
The time may be given in one of the following formats:
- *YYYY-MM-DD HH:MM:SS*
- End time is the date and time given.
+ *YYYY-MM-DD HH:MM:SS*
+ End time is the date and time given.
- *HH:MM:SS*
- End time is the time given, today.
+ *HH:MM:SS*
+ End time is the time given, today.
- *+HH:MM:SS*
- End time is HH hours, MM minutes, SS seconds in the future (counted
- from the moment that program starts).
+ *+HH:MM:SS*
+ End time is HH hours, MM minutes, SS seconds in the future
+ (counted from the moment that program starts).
- *+secs*
- End time is *secs* seconds in the future.
+ *+secs*
+ End time is *secs* seconds in the future.
- For example to run the program for 3 minutes you could do:
+ For example to run the program for 3 minutes you could do:
- virt-top --end-time +00:03:00
+ virt-top --end-time +00:03:00
- or:
+ or:
- virt-top --end-time +180
+ virt-top --end-time +180
- Not every version of virt-top supports this option - it depends how the
- program was compiled (see *README* file in the source distribution for
- details).
+ Not every version of virt-top supports this option - it depends how
+ the program was compiled (see *README* file in the source
+ distribution for details).
--help
- Display usage summary.
+ Display usage summary.
+
+ --version
+ Display version number and exit.
KEYS
Note that keys are case sensitive. For example use upper-case *P* (shift
*s* or *d*
Change the delay between screen updates.
+ *B* Toggle Block I/O statistics so they are shown in either bytes or
+ requests.
+
*0* (number 0)
Show the normal list of domains display.
*P* Sort by %CPU.
- *M* Sort by memory.
+ *M* Sort by total memory. Note that this shows the total memory
+ allocated to the guest, not the memory being used.
*T* Sort by total time.
script *true|false*
Sets script mode.
+ stream *true|false*
+ Sets stream mode.
+
+ block-in-bytes *true|false*
+ Show block device statistics in bytes.
+
end-time *time*
Set the time at which the program exits. See above for the time
formats supported.
file override options specified on the command line. This is a bug and
this behaviour may change in the future.
+NOTES
+ Block I/O statistics
+ This I/O value is the amount of I/O since the previous iteration of
+ virt-top. To calculate speed of I/O, you should divide the number by
+ delay secs.
+
+ NETWORK RX BYTES AND PACKETS
+ Libvirt/virt-top has no way to know that a packet transmitted to a guest
+ was received (eg. if the guest is not listening). In the network RX
+ stats, virt-top reports the packets transmitted to the guest, on the
+ basis that the guest might receive them.
+
+ In particular this includes broadcast packets. Because of the way that
+ Linux bridges work, if the guest is connected to a bridge, it will
+ probably see a steady "background noise" of RX packets even when the
+ network interface is idle or down. These are caused by STP packets
+ generated by the bridge.
+
SEE ALSO
- top(1), virsh(1), xm(1), xentop(1), <http://www.libvirt.org/>,
- <http://et.redhat.com/~rjones/>, <http://caml.inria.fr/>
+ top(1), virsh(1), <http://www.libvirt.org/ocaml/>,
+ <http://www.libvirt.org/>, <http://people.redhat.com/~rjones/>,
+ <http://caml.inria.fr/>
AUTHORS
Richard W.M. Jones <rjones @ redhat . com>
COPYRIGHT
- (C) Copyright 2007 Red Hat Inc., Richard W.M. Jones http://libvirt.org/
+ (C) Copyright 2007-2011 Red Hat Inc., Richard W.M. Jones
+ http://libvirt.org/
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
submit with your bug report.
3. Get version of virt-top and version of libvirt.
- In virt-top, press the *h* (help) key, and write down the version of
- virt-top and the version of libvirt. They are shown in the first
- line.
+ Use:
+
+ virt-top --version
+
+ If you can get the precise version of libvirt you are using then
+ that too is helpful.
4. Submit a bug report.
Go to <https://bugzilla.redhat.com/> and enter a new bug. Please
git.annexia.org / virt-top.git / blobdiff