[spice-server v2] doc: Document G_MESSAGES_DEBUG use

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Explain how to get more verbose logs out of spice-server

Signed-off-by: Christophe Fergeau <cfergeau@xxxxxxxxxx>
---
 docs/manual/manual.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/manual/manual.txt b/docs/manual/manual.txt
index 99f6a5c84..9de3c4701 100644
--- a/docs/manual/manual.txt
+++ b/docs/manual/manual.txt
@@ -1203,10 +1203,20 @@ Server side
 
 If the virtual machine was started using QEMU directly, SPICE server logs will be output to
 your console stdout.
+
 When using libvirt, logs are located in `/var/log/libvirt/qemu/` for the qemu
 system instance (`qemu:///system`), and in `~/.cache/libvirt/qemu/log` for the
 qemu session instance (`qemu:///session`).
 
+It's possible to get more verbose output by setting the `G_MESSAGES_DEBUG`
+environment variable to `Spice` or `all` before starting QEMU as described in
+https://developer.gnome.org/glib/stable/glib-running.html[GLib documentation].
+
+When using libvirt, the environment variable needs to be set from the XML
+domain definition as described in
+https://libvirt.org/drvqemu.html#qemucommand[libvirt documentation].
+
+
 Client side
 -----------
 
-- 
2.20.1

_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/spice-devel




[Index of Archives]     [Linux Virtualization]     [Linux Virtualization]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]