To make it easier to investigate problems with async event
delivery, add two more debugging lines
* daemon/remote.c: Debug when an event is queued for dispatch
* src/remote/remote_driver.c: Debug when an event is received
for processing
---
daemon/remote.c | 2 ++
src/remote/remote_driver.c | 1 +
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/daemon/remote.c b/daemon/remote.c
index aa6a1a4..f8f6ffa 100644
--- a/daemon/remote.c
+++ b/daemon/remote.c
@@ -5670,6 +5670,8 @@ remoteDispatchDomainEventSend (struct qemud_client *client,
msg->async = 1;
msg->bufferLength = len;
msg->bufferOffset = 0;
+
+ VIR_DEBUG("Queue event %d %d", procnr, msg->bufferLength);
qemudClientMessageQueuePush(&client->tx, msg);
qemudUpdateClientEvent(client);
diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c
index 347b844..64af91c 100644
--- a/src/remote/remote_driver.c
+++ b/src/remote/remote_driver.c
@@ -9865,6 +9865,7 @@ processCallDispatch(virConnectPtr conn, struct private_data *priv,
break;
case REMOTE_MESSAGE: /* Async notifications */
+ VIR_DEBUG("Dispatch event %d %d", hdr.proc, priv->bufferLength);
rv = processCallDispatchMessage(conn, priv, flags & REMOTE_CALL_IN_OPEN,
&hdr, &xdr);
break;
--
1.7.3.5