From 372c6f96f7a3fd02f2f8227b1c4faaee9d5d2355 Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Wed, 5 Sep 2007 14:32:13 +0000 Subject: [PATCH] * docs/libvir.html docs/uri.html: remove references to libvirt_qemud and replace them with libvirtd Daniel --- ChangeLog | 5 +++++ docs/libvir.html | 13 +++++++------ docs/uri.html | 13 +++++++------ 3 files changed, 19 insertions(+), 12 deletions(-) diff --git a/ChangeLog b/ChangeLog index 93dd8d8fef..15cd5e9509 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Wed Sep 5 16:31:00 CEST 2007 Daniel Veillard + + * docs/libvir.html docs/uri.html: remove references to libvirt_qemud + and replace them with libvirtd + Mon Sep 3 18:29:05 CEST 2007 Daniel Veillard * src/openvz_conf.c src/openvz_conf.h src/openvz_driver.c: a bit diff --git a/docs/libvir.html b/docs/libvir.html index dcede5519d..94567c66bb 100644 --- a/docs/libvir.html +++ b/docs/libvir.html @@ -2478,18 +2478,19 @@ use the URI xen:///.

To use QEMU support in libvirt you must be running the -libvirt_qemud daemon. The purpose of this +libvirtd daemon (named libvirt_qemud +in releases prior to 0.3.0). The purpose of this daemon is to manage qemu instances.

-The libvirt_qemud daemon can be run in two ways. It may +The libvirtd daemon can be run in two ways. It may be started by init scripts when the machine boots and run in "system -mode" (libvirt_qemud --system), in which case it manages +mode" (libvirtd --system), in which case it manages qemu instances on behalf of all users of the machine. It may be also be started by the local user in what is known as "session mode" -(libvirt_qemud --session), to manage qemu instances for -just the current user. If no libvirt_qemud is running at +(libvirtd --session), to manage qemu instances for +just the current user. If no libvirtd is running at all, then the qemu driver starts one running in session mode.

@@ -2503,7 +2504,7 @@ So to connect to the daemon, one of two different URIs is used:

-(If you do libvirt_qemud --help, the daemon will print +(If you do libvirtd --help, the daemon will print out the paths of the Unix domain socket(s) that it listens on in the various different modes).

diff --git a/docs/uri.html b/docs/uri.html index be365751ae..9b4b23bb1c 100644 --- a/docs/uri.html +++ b/docs/uri.html @@ -47,23 +47,24 @@ To access a Xen hypervisor running on the local machine use the URI xen:///.

qemu:///... QEMU and KVM URIs

To use QEMU support in libvirt you must be running the -libvirt_qemud daemon. The purpose of this +libvirtd daemon (named libvirt_qemud +in releases prior to 0.3.0). The purpose of this daemon is to manage qemu instances.

-The libvirt_qemud daemon can be run in two ways. It may +The libvirtd daemon can be run in two ways. It may be started by init scripts when the machine boots and run in "system -mode" (libvirt_qemud --system), in which case it manages +mode" (libvirtd --system), in which case it manages qemu instances on behalf of all users of the machine. It may be also be started by the local user in what is known as "session mode" -(libvirt_qemud --session), to manage qemu instances for -just the current user. If no libvirt_qemud is running at +(libvirtd --session), to manage qemu instances for +just the current user. If no libvirtd is running at all, then the qemu driver starts one running in session mode.

So to connect to the daemon, one of two different URIs is used:

  • qemu:///system connects to a system mode daemon.
  • qemu:///session connects to a session mode daemon.

-(If you do libvirt_qemud --help, the daemon will print +(If you do libvirtd --help, the daemon will print out the paths of the Unix domain socket(s) that it listens on in the various different modes).

-- GitLab