NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-11 07:55:58 -06:00
Code Issues Packages Projects Releases Wiki Activity

* docs/libvir.html docs/uri.html: update docs about the libvirt

Browse Source 
daemon startup when using QEmu/KVM.
Daniel
This commit is contained in:
Daniel Veillard 2007-11-15 17:07:28 +00:00
parent d5117af382
commit 9ae4f3d27e
3 changed files with 15 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
Thu Nov 15 18:06:15 CET 2007 Daniel Veillard <veillard@redhat.com>
* docs/libvir.html docs/uri.html: update docs about the libvirt
daemon startup when using QEmu/KVM.
Thu Nov 15 14:00:04 CET 2007 Jim Meyering <meyering@redhat.com>
Make "make distcheck" work.

14
docs/libvir.html
View File

@ -2571,15 +2571,11 @@ daemon is to manage qemu instances.
</p>
<p>
The <code>libvirtd</code> daemon can be run in two ways. It may
be started by init scripts when the machine boots and run in "system
mode" (<code>libvirtd --system</code>), 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"
(<code>libvirtd --session</code>), to manage qemu instances for
just the current user. If no <code>libvirtd</code> is running at
all, then the qemu driver starts one running in session mode.
</p>
The <code>libvirtd</code> daemon should be started by the
init scripts when the machine boots. It should appear as
a process <code>libvirtd --daemon</code> running as root
in the background and will handle qemu instances on behalf
of all users of the machine (among other things). </p>
<p>
So to connect to the daemon, one of two different URIs is used:

14
docs/uri.html
View File

@ -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.
</p><p>
The <code>libvirtd</code> daemon can be run in two ways. It may
be started by init scripts when the machine boots and run in "system
mode" (<code>libvirtd --system</code>), 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"
(<code>libvirtd --session</code>), to manage qemu instances for
just the current user. If no <code>libvirtd</code> is running at
all, then the qemu driver starts one running in session mode.
</p><p>
The <code>libvirtd</code> daemon should be started by the
init scripts when the machine boots. It should appear as
a process <code>libvirtd --daemon</code> running as root
in the background and will handle qemu instances on behalf
of all users of the machine (among other things). </p><p>
So to connect to the daemon, one of two different URIs is used:
</p><ul><li> <code>qemu:///system</code> connects to a system mode daemon. </li>
<li> <code>qemu:///session</code> connects to a session mode daemon. </li>