From: Peter Krempa <pkrempa@redhat.com>

The debug message recording the string we've got to process didn't
specify which monitor object the reply comes from which makes it harder
to follow what's happening in cases when multiple VMs communicate (e.g.
when reconnecting at startup).

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
---
 src/qemu/qemu_monitor_json.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/qemu/qemu_monitor_json.c b/src/qemu/qemu_monitor_json.c
index 28f7d93834..21f4d613b7 100644
--- a/src/qemu/qemu_monitor_json.c
+++ b/src/qemu/qemu_monitor_json.c
@@ -214,7 +214,7 @@ qemuMonitorJSONIOProcessLine(qemuMonitor *mon,
 {
     g_autoptr(virJSONValue) obj = NULL;

-    VIR_DEBUG("Line [%s]", line);
+    VIR_DEBUG("mon=0x%p line=[%s]", mon, line);

     if (!(obj = virJSONValueFromString(line)))
         return -1;
-- 
2.55.0