From 2222bd245979a85bcea1a39e8bb0baa1f88af035 Mon Sep 17 00:00:00 2001
From: "Daniel P. Berrange" <berrange@redhat.com>
Date: Thu, 27 Jan 2011 15:06:05 +0000
Subject: [PATCH] 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
---
 daemon/remote.c            | 2 ++
 src/remote/remote_driver.c | 1 +
 2 files changed, 3 insertions(+)

diff --git a/daemon/remote.c b/daemon/remote.c
index de45ff9e1b..d53b466408 100644
--- 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 c33a930464..4ca0d3b646 100644
--- 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;