On 02/02/2011 05:18 AM, Daniel P. Berrange wrote:
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(-)
ACK.
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);
Technically, this should be "%d %u", but since we'll never send a 2GB message and the compiler doesn't warn, I don't care. -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org