On Wed, 2014-11-26 at 17:38 +, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] segv in osevent_release_nexus with
> libxl backend to libvirt"):
> > I don't know if this helps but on the 3 occasions I've just looked at
> > the ev passed to
Ian Campbell writes ("Re: [Xen-devel] segv in osevent_release_nexus with libxl
backend to libvirt"):
> I don't know if this helps but on the 3 occasions I've just looked at
> the ev passed to libxl__ev_fd_deregister contains an fd which
> corresponds to a still open
On Wed, 2014-11-26 at 15:40 +, Ian Campbell wrote:
> (adding xen-devel which I forgot first time around)
>
> On Wed, 2014-11-26 at 15:21 +, Ian Jackson wrote:
> > Ian Campbell writes ("segv in osevent_release_nexus with libxl backend to
> > libvirt"):
> > > I'm seeing quite a few of these
(adding xen-devel which I forgot first time around)
On Wed, 2014-11-26 at 15:21 +, Ian Jackson wrote:
> Ian Campbell writes ("segv in osevent_release_nexus with libxl backend to
> libvirt"):
> > I'm seeing quite a few of these when shutting down domains:
> ...
> > This is on ARM but I don't t
Hi,
I'm seeing quite a few of these when shutting down domains:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb47f9420 (LWP 3322)]
0xb16d2f20 in osevent_release_nexus (gc=0xb47f88bc,
nexi_idle=0x2a0968fc, nexus=0x0) at libxl_event.c:119
