From ad0221b4eed02049674ca4584fa4c585f0f3203f Mon Sep 17 00:00:00 2001 From: "Richard W.M. Jones" Date: Tue, 8 Mar 2011 10:41:48 +0000 Subject: docs: Fix documentation for virt-top -c option. Because of changes in libvirt, this no longer connects to Xen by default. Instead the default is to connect to the libvirt default hypervisor (which could be Xen, KVM or others). Update the --help documentation and manual page accordingly. --- virt-top/virt-top.pod | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) (limited to 'virt-top/virt-top.pod') diff --git a/virt-top/virt-top.pod b/virt-top/virt-top.pod index d479b63..225c5ea 100755 --- a/virt-top/virt-top.pod +++ b/virt-top/virt-top.pod @@ -43,16 +43,21 @@ Batch mode. In this mode keypresses are ignored. =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 +See the libvirt documentation at L +for further information. =item B<-d delay> -- cgit