Add a little more debugging for async events

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

diff --git a/daemon/remote.c b/daemon/remote.c
index de45ff9e1b4860a7b3c3f6270fa0954584a8d9f2..d53b46640801ea64f7889291f4b953c214fe898a 100644 (file)
--- a/daemon/remote.c
+++ b/daemon/remote.c
@@ -5693,6 +5693,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 c33a930464fdc8110dd73d558d8e5474c275db46..4ca0d3b646c038d91bff882da714977fc3dceb16 100644 (file)
--- a/src/remote/remote_driver.c
+++ b/src/remote/remote_driver.c
@@ -9890,6 +9890,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;