On 11/23/2015 01:59 PM, Jim Fehlig wrote:
>
> Thanks for your comments and ACK'ing the change . I'll submit a V2 that
> retains
> handling of shutdown event in a thread.
While testing V2, I noticed occasionally missing a shutdown event. I can see
from the logs that domain_death_xswatch_callback i
On 11/23/2015 04:24 AM, Ian Jackson wrote:
> Jim Fehlig writes ("[PATCH RFC] libxl: use libxl_event_wait to process libxl
> events"):
>> Prior to this patch, libxl events were delivered to libvirt via
>> the libxlDomainEventHandler callback registered with libxl.
>> Documenation in $xensrc/tools/l
Jim Fehlig writes ("[PATCH RFC] libxl: use libxl_event_wait to process libxl
events"):
> Prior to this patch, libxl events were delivered to libvirt via
> the libxlDomainEventHandler callback registered with libxl.
> Documenation in $xensrc/tools/libxl/libxl_event.h states that the
> callback "may
Am Fri, 13 Nov 2015 14:36:54 -0700
schrieb Jim Fehlig :
Hi,
i have tested the patches provide by Jim Fehlig.
The setup consist of xen 4.6.0 with libvirt 1.2.19 and the patches.
As i describe in my posting in the libvirt-user list
(https://www.redhat.com/archives/libvir-list/2015-November/msg0013
Prior to this patch, libxl events were delivered to libvirt via
the libxlDomainEventHandler callback registered with libxl.
Documenation in $xensrc/tools/libxl/libxl_event.h states that the
callback "may occur on any thread in which the application calls
libxl". This can result in deadlock since ma