[PATCH 6/6] docs: compiling: Add notes on starting compiled libvirt daemons

[Peter Krempa]

In the basic configuration with monolithic libvirtd users are required
to also start virtlogd. Add a general note with a specific example
hinting that this is needed.

Signed-off-by: Peter Krempa <pkrempa at redhat.com>
---
 docs/compiling.rst | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/docs/compiling.rst b/docs/compiling.rst
index 1d06136ca6..0b8e2b328d 100644
--- a/docs/compiling.rst
+++ b/docs/compiling.rst
@@ -9,8 +9,8 @@ Installing from distribution repositories

 This is the recommended option to install libvirt. Libvirt is present in the
 package repositories of all major distributions. Installing a package from the
-package manager ensures that it's properly compiled, installed, and updated
-during the lifecycle of the distribution.
+package manager ensures that it's properly compiled, installed, started, and
+updated during the lifecycle of the distribution.

 For users who wish to use the most recent version, certain distributions also
 allow installing the most recent versions of virtualization packages:
@@ -151,6 +151,10 @@ It is also possible to run virsh directly from the build tree using the
    /home/to/your/checkout/build
    $ ./run ./tools/virsh ....

+**Note:** The libvirt project provides `multiple daemons <daemons.html>`__ and
+the above steps may replace only some of them with the custom compiled instances.
+In most cases this should work but keep that fact in mind.
+
 Installing compiled binaries
 ----------------------------

@@ -179,3 +183,8 @@ putting **sudo** before it.
 After installation you you **may** have to run ``ldconfig`` or a similar
 utility to update your list of installed shared libs, or adjust the paths where
 the system looks for binaries and shared libraries.
+
+The libvirt project provides `multiple daemons <daemons.html>`__ based on your
+configuration. You have to ensure that you start the appropriate processes for
+the freshly installed libvirt to be usable (e.g. even monolithic ``libvirtd``
+requires in most configurations that ``virtlogd`` is started).
-- 
2.37.1