=item B<-c uri> or B<--connect uri>
-Connect to URI given. The default is to connect to the Xen
-hypervisor.
+Connect to the libvirt URI given.
To connect to QEMU/KVM you would normally do I<-c qemu:///system>
+To connect to Xen on the same host, do I<-c xen:///>
+
To connect to libvirtd on a remote machine you would normally do
-I<-c xen://host/>
+I<-c qemu://host/system>
+
+If this option is not given then virt-top connects by default
+to whatever is the default hypervisor for libvirt, although
+this can be overridden by setting environment variables.
-Full details on connection URIs is available at
-L<http://libvirt.org/uri.html>
+See the libvirt documentation at L<http://libvirt.org/uri.html>
+for further information.
=item B<-d delay>
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.
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.
the network interface is idle or down. These are caused by STP
packets generated by the bridge.
+=head2 DEBUGGING LIBVIRT ISSUES
+
+virt-top tries to turn libvirt errors into informative messages.
+However if libvirt initialization fails then this is not possible.
+Instead you will get an obscure error like:
+
+ libvir: error : Unknown failure
+ Fatal error: exception Libvirt.Virterror(...)
+
+To see the cause of libvirt errors in more detail, enable libvirt
+debugging by setting this environment variable:
+
+ export LIBVIRT_DEBUG=1
+
=head1 SEE ALSO
L<top(1)>,
=head1 COPYRIGHT
-(C) Copyright 2007-2011 Red Hat Inc., Richard W.M. Jones
+(C) Copyright 2007-2012 Red Hat Inc., Richard W.M. Jones
http://libvirt.org/
This program is free software; you can redistribute it and/or modify