From: Daniel Veillard
-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" (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"
-(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.
-
libvirtd
daemon should be started by the
+init scripts when the machine boots. It should appear as
+a process libvirtd --daemon
running as root
+in the background and will handle qemu instances on behalf
+of all users of the machine (among other things).
So to connect to the daemon, one of two different URIs is used: diff --git a/docs/uri.html b/docs/uri.html index 9b4b23bb1c..4d3ef35244 100644 --- a/docs/uri.html +++ b/docs/uri.html @@ -51,15 +51,11 @@ To use QEMU support in libvirt you must be running the in releases prior to 0.3.0). The purpose of this daemon is to manage qemu instances.
-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" (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"
-(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.
-
+The libvirtd
daemon should be started by the
+init scripts when the machine boots. It should appear as
+a process libvirtd --daemon
running as root
+in the background and will handle qemu instances on behalf
+of all users of the machine (among other things).
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.