Disable domain CPU stats in CSV output.
+=item B<--no-csv-mem>
+
+Disable domain memory stats in CSV output.
+
=item B<--no-csv-block>
Disable domain block device stats in CSV output.
Script mode. There will be no user interface. This is most useful
when used together with the I<--csv> and I<-n> options.
+=item B<--stream>
+
+Stream mode. All output is sent to stdout. This can be used from
+shell scripts etc. There is no user interface.
+
+=item B<--block-in-bytes>
+
+Show I/O statistics in Bytes. Default is shown in the number of Requests.
+
=item B<--end-time time>
The program will exit at the I<time> given.
Change the delay between screen updates.
+=item I<B>
+
+Toggle Block I/O statistics so they are shown in either bytes or requests.
+
=item I<0> (number 0)
Show the normal list of domains display.
Enable or disable domain CPU stats in CSV output.
+=item B<csv-mem> I<true|false>
+
+Enable or disable domain memory stats in CSV output.
+
=item B<csv-block> I<true|false>
Enable or disable domain block device stats in CSV output.
Sets script mode.
+=item B<stream> I<true|false>
+
+Sets stream mode.
+
+=item B<block-in-bytes> I<true|false>
+
+Show block device statistics in bytes.
+
=item B<end-time> I<time>
Set the time at which the program exits. See above for the
the init file override options specified on the command line.
This is a bug and this behaviour may change in the future.
+=head1 NOTES
+
+=head2 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.
+
+=head2 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.
+
=head1 SEE ALSO
L<top(1)>,