On 3/5/21 10:45 AM, Andrea Bolognani wrote:
On Thu, 2021-03-04 at 20:55 +0100, Michal Privoznik wrote:
Surprisingly, we never documented the relationship between connection URI and the location of qemu.conf. Users might wonder what qemu.conf is loaded when they are connecting to the session daemon or embed URI. And what to do if the file doesn't exist for the URI they're using.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- docs/drvqemu.html.in | 39 +++++++++++++++++++++++++++++++++++++ docs/manpages/libvirtd.rst | 20 +++++++++++++++++++ docs/manpages/virtqemud.rst | 22 +++++++++++++++++++++ 3 files changed, 81 insertions(+)
Excellent stuff, thanks for tackling this!
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Now, since no good deed ever goes unpunished :) how would you feel about doing something similar for lxc.conf and libxl.conf? You can pretty much use the exact same text for both.
Absolutely.
We also have qemu-lockd.conf and libxl-lockd.conf, but I have no idea what those are used for.
They are used for configuring the way we lock disks and so called leases (for virtlockd). This is documented in docs/kbase/locking-lockd.rst nevertheless, this table I'm inventing here should document those too. Michal