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

* docs/libvir.html docs/uri.html: remove references to libvirt_qemud

Browse Source 
and replace them with libvirtd
Daniel
This commit is contained in:
Daniel Veillard 2007-09-05 14:32:13 +00:00
parent 5196e6cab7
commit 372c6f96f7
3 changed files with 19 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
Wed Sep 5 16:31:00 CEST 2007 Daniel Veillard <veillard@redhat.com>
* 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 <veillard@redhat.com> Mon Sep 3 18:29:05 CEST 2007 Daniel Veillard <veillard@redhat.com>
* src/openvz_conf.c src/openvz_conf.h src/openvz_driver.c: a bit * src/openvz_conf.c src/openvz_conf.h src/openvz_driver.c: a bit

13
docs/libvir.html
View File

@ -2478,18 +2478,19 @@ use the URI <code>xen:///</code>.
<p> <p>
To use QEMU support in libvirt you must be running the To use QEMU support in libvirt you must be running the
<code>libvirt_qemud</code> daemon. The purpose of this <code>libvirtd</code> daemon (named <code>libvirt_qemud</code>
in releases prior to 0.3.0). The purpose of this
daemon is to manage qemu instances. daemon is to manage qemu instances.
</p> </p>
<p> <p>
The <code>libvirt_qemud</code> daemon can be run in two ways. It may 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 be started by init scripts when the machine boots and run in "system
mode" (<code>libvirt_qemud --system</code>), in which case it manages mode" (<code>libvirtd --system</code>), in which case it manages
qemu instances on behalf of all users of the machine. It may be also 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" be started by the local user in what is known as "session mode"
(<code>libvirt_qemud --session</code>), to manage qemu instances for (<code>libvirtd --session</code>), to manage qemu instances for
just the current user. If no <code>libvirt_qemud</code> is running at just the current user. If no <code>libvirtd</code> is running at
all, then the qemu driver starts one running in session mode. all, then the qemu driver starts one running in session mode.
</p> </p>
@ -2503,7 +2504,7 @@ So to connect to the daemon, one of two different URIs is used:
</ul> </ul>
<p> <p>
(If you do <code>libvirt_qemud --help</code>, the daemon will print (If you do <code>libvirtd --help</code>, the daemon will print
out the paths of the Unix domain socket(s) that it listens on in out the paths of the Unix domain socket(s) that it listens on in
the various different modes). the various different modes).
</p> </p>

13
docs/uri.html
View File

@ -47,23 +47,24 @@ To access a Xen hypervisor running on the local machine
use the URI <code>xen:///</code>. use the URI <code>xen:///</code>.
</p><h3><a name="URI_qemu" id="URI_qemu">qemu:///... QEMU and KVM URIs</a></h3><p> </p><h3><a name="URI_qemu" id="URI_qemu">qemu:///... QEMU and KVM URIs</a></h3><p>
To use QEMU support in libvirt you must be running the To use QEMU support in libvirt you must be running the
<code>libvirt_qemud</code> daemon. The purpose of this <code>libvirtd</code> daemon (named <code>libvirt_qemud</code>
in releases prior to 0.3.0). The purpose of this
daemon is to manage qemu instances. daemon is to manage qemu instances.
</p><p> </p><p>
The <code>libvirt_qemud</code> daemon can be run in two ways. It may 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 be started by init scripts when the machine boots and run in "system
mode" (<code>libvirt_qemud --system</code>), in which case it manages mode" (<code>libvirtd --system</code>), in which case it manages
qemu instances on behalf of all users of the machine. It may be also 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" be started by the local user in what is known as "session mode"
(<code>libvirt_qemud --session</code>), to manage qemu instances for (<code>libvirtd --session</code>), to manage qemu instances for
just the current user. If no <code>libvirt_qemud</code> is running at just the current user. If no <code>libvirtd</code> is running at
all, then the qemu driver starts one running in session mode. all, then the qemu driver starts one running in session mode.
</p><p> </p><p>
So to connect to the daemon, one of two different URIs is used: 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> </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> <li> <code>qemu:///session</code> connects to a session mode daemon. </li>
</ul><p> </ul><p>
(If you do <code>libvirt_qemud --help</code>, the daemon will print (If you do <code>libvirtd --help</code>, the daemon will print
out the paths of the Unix domain socket(s) that it listens on in out the paths of the Unix domain socket(s) that it listens on in
the various different modes). the various different modes).
</p><p> </p><p>