Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-12-04 Thread Shu Ming
I think the best way is to let libvirt to catch the abnormal exit signal for the application. A default signal handler in libvirt will un-register the event before the application exists abnormally. On 2011-12-2 18:52, ShaoHe Feng wrote: Hi Eric, There's a question about register an Event.

Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-12-02 Thread ShaoHe Feng
Hi Eric, There's a question about register an Event. When user starts an application call remoteDispatchDomainEventsRegisterAny to register an event. And for some reasons, this application breaks down. Will the libvirtd daemon know the application breaks down? And delete the event? if not,

Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-10-14 Thread Eric Blake
On 10/13/2011 08:53 PM, shu ming wrote: Also I think it would be better if we were able to connect to explicit JSON events, rather than a catch all. THe number of events from QEMU is only going to increase over time as it does, a 'catch all' becomes increasingly bandwidth wasteful. If I

Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-10-13 Thread Daniel P. Berrange
On Tue, Oct 11, 2011 at 08:46:06AM -0500, Adam Litke wrote: On Mon, Oct 10, 2011 at 11:54:08PM +0800, shao...@linux.vnet.ibm.com wrote: From: Shaohe Feng shao...@linux.vnet.ibm.com Basically, this feature can go along with qemu monitor passthrough. That way, if we use new commands in the

Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-10-13 Thread Adam Litke
On Thu, Oct 13, 2011 at 10:54:13AM +0100, Daniel P. Berrange wrote: On Tue, Oct 11, 2011 at 08:46:06AM -0500, Adam Litke wrote: On Mon, Oct 10, 2011 at 11:54:08PM +0800, shao...@linux.vnet.ibm.com wrote: From: Shaohe Feng shao...@linux.vnet.ibm.com Basically, this feature can go along

Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-10-13 Thread shu ming
On 2011-10-13 17:54, Daniel P. Berrange wrote: On Tue, Oct 11, 2011 at 08:46:06AM -0500, Adam Litke wrote: On Mon, Oct 10, 2011 at 11:54:08PM +0800, shao...@linux.vnet.ibm.com wrote: From: Shaohe Fengshao...@linux.vnet.ibm.com Basically, this feature can go along with qemu monitor

Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-10-11 Thread Xu, He Jie
On 2011?10?10? 23:54, shao...@linux.vnet.ibm.com wrote: From: Shaohe Fengshao...@linux.vnet.ibm.com Basically, this feature can go along with qemu monitor passthrough. That way, if we use new commands in the monitor that generate new events, we want some way to receive those new events too.

Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-10-11 Thread Adam Litke
On Mon, Oct 10, 2011 at 11:54:08PM +0800, shao...@linux.vnet.ibm.com wrote: From: Shaohe Feng shao...@linux.vnet.ibm.com Basically, this feature can go along with qemu monitor passthrough. That way, if we use new commands in the monitor that generate new events, we want some way to

Re: [libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-10-10 Thread Sheldon
On 10/10/2011 11:54 PM, shao...@linux.vnet.ibm.com wrote: From: Shaohe Fengshao...@linux.vnet.ibm.com Basically, this feature can go along with qemu monitor passthrough. That way, if we use new commands in the monitor that generate new events, we want some way to receive those new events

[libvirt] [PATCH] add a default event handle, to passthough the new events come from qemu

2011-10-10 Thread shaohef
From: Shaohe Feng shao...@linux.vnet.ibm.com Basically, this feature can go along with qemu monitor passthrough. That way, if we use new commands in the monitor that generate new events, we want some way to receive those new events too. In order to test this patch, see the attached python test