Displaying 6 results from an estimated 6 matches for "libxl_osevent_occurred_timeout".
2013 Dec 19
2
Re: About debugging of libvirt.
...e error. Following are the stacktrace which i got.
Kindly refer the following logs for full information:
****
[New Thread 0x7f8503695700 (LWP 20012)]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007f84f671281e in libxl_osevent_occurred_timeout (ctx=<optimized
out>, for_libxl=0x7f8503bbbc38) at libxl_event.c:1039
#2 0x00007f84f69439c7 in libxlDomainObjTimerCallback (timer=<optimized
out>, timer_info=0x7f8503bb5930) at libxl/libxl_domain.c:216
#3 0x00007f8502ba6f7d in virEventPollDispatchTimeouts () at
util/vireventpoll.c:451...
2013 Dec 19
1
Re: About debugging of libvirt.
...c:161
#4 0x00007fc335097b50 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#5 0x00007fc3349daa3d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#6 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7fc337c4d7c0 (LWP 29169)):
#0 0x0000000000000000 in ?? ()
#1 0x00007fc32ace881e in libxl_osevent_occurred_timeout (ctx=<optimized
out>, for_libxl=0x7fc3380edf38) at libxl_event.c:1039
#2 0x00007fc32af199c7 in libxlDomainObjTimerCallback (timer=<optimized
out>, timer_info=0x7fc3380e3310) at libxl/libxl_domain.c:216
#3 0x00007fc33717cf7d in virEventPollDispatchTimeouts () at
util/vireventpoll.c:451...
2013 Dec 19
0
Re: About debugging of libvirt.
...> Kindly refer the following logs for full information:
>
> ****
> [New Thread 0x7f8503695700 (LWP 20012)]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000000 in ?? ()
> (gdb) bt
> #0 0x0000000000000000 in ?? ()
> #1 0x00007f84f671281e in libxl_osevent_occurred_timeout (ctx=<optimized
> out>, for_libxl=0x7f8503bbbc38) at libxl_event.c:1039
> #2 0x00007f84f69439c7 in libxlDomainObjTimerCallback (timer=<optimized
> out>, timer_info=0x7f8503bb5930) at libxl/libxl_domain.c:216
> #3 0x00007f8502ba6f7d in virEventPollDispatchTimeouts () at
>...
2013 Dec 19
2
Re: About debugging of libvirt.
i installed both xen-4.2.1 and libvirt-1.2.0 from the source only. i moved
with the latest version of libvrirt.
i did the gdb in libvirt-1.2.0 and i raised the bug. Please find the
following link for the bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1044838
regards,
cooldharma06.
On Wed, Dec 18, 2013 at 6:33 PM, Michal Privoznik <mprivozn@redhat.com>wrote:
> On 18.12.2013
2013 Feb 24
2
[xen-4.2-testing test] 16260: regressions - FAIL
...commit 6f0f339dd4378d062a211969f45cd23af12bf386
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Wed Jan 23 16:53:11 2013 +0000
libxl: fix stale timeout event callback race
Because there is not necessarily any lock held at the point the
application (eg, libvirt) calls libxl_osevent_occurred_timeout, in a
multithreaded program those calls may be arbitrarily delayed in
relation to other activities within the program.
Specifically this means when ->timeout_deregister returns, libxl does
not know whether it can safely dispose of the for_libxl value or
whether it needs...
2013 Mar 25
86
[PATCH 00/28] libxl: ocaml: improve the bindings
The following series of patches fill in most of the gaps in the OCaml bindings
to libxl, to make them useful for clients such as xapi/xenopsd (from XCP).
There are a number of bugfixes to the existing bindings as well. I have an
experimental version of xenopsd that successfully uses the new bindings.
An earlier version of the first half of the series was submitted to the last
by Ian Campbell on