AL13N wrote:
>> AL13N wrote:
>>
>>> Op woensdag 20 maart 2013 08:42:52 schreef Jim Fehlig:
>>>
>>>
AL13N wrote:
> Thread 1 (Thread 0x7fdef683b800 (LWP 20522)):
> #0 0x in ?? ()
> #1 0x7fdee9a72dc7 in libxl_osevent_occurred_timeou
Hi,
Libvirtd from latest git (HEAD fc8c1787) is segfaulting when I try to
restore a previously saved domain (backtrace below).
I was testing a custom QEMU when it happened first time, but it also
happens with latest qemu.git (HEAD 162cbbd17).
What I did to run libvirt from source was:
1. Build
> AL13N wrote:
>> Op woensdag 20 maart 2013 08:42:52 schreef Jim Fehlig:
>>
>>> AL13N wrote:
>>>
Thread 1 (Thread 0x7fdef683b800 (LWP 20522)):
#0 0x in ?? ()
#1 0x7fdee9a72dc7 in libxl_osevent_occurred_timeout
(ctx=>>> out>, for_libxl=0x7fdedc001608) at lib
AL13N wrote:
> Op woensdag 20 maart 2013 08:42:52 schreef Jim Fehlig:
>
>> AL13N wrote:
>>
>>> Thread 1 (Thread 0x7fdef683b800 (LWP 20522)):
>>> #0 0x in ?? ()
>>> #1 0x7fdee9a72dc7 in libxl_osevent_occurred_timeout (ctx=>> out>, for_libxl=0x7fdedc001608) at libxl_even
Op woensdag 20 maart 2013 08:42:52 schreef Jim Fehlig:
> AL13N wrote:
> > Thread 1 (Thread 0x7fdef683b800 (LWP 20522)):
> > #0 0x in ?? ()
> > #1 0x7fdee9a72dc7 in libxl_osevent_occurred_timeout (ctx= > out>, for_libxl=0x7fdedc001608) at libxl_event.c:1039
> > #2 0x7fdee9
Op woensdag 20 maart 2013 08:42:52 schreef Jim Fehlig:
> AL13N wrote:
> > Thread 1 (Thread 0x7fdef683b800 (LWP 20522)):
> > #0 0x in ?? ()
> > #1 0x7fdee9a72dc7 in libxl_osevent_occurred_timeout (ctx= > out>, for_libxl=0x7fdedc001608) at libxl_event.c:1039
> > #2 0x7fdee9
AL13N wrote:
> Thread 1 (Thread 0x7fdef683b800 (LWP 20522)):
> #0 0x in ?? ()
> #1 0x7fdee9a72dc7 in libxl_osevent_occurred_timeout (ctx= out>,
> for_libxl=0x7fdedc001608) at libxl_event.c:1039
> #2 0x7fdee9c9ff87 in libxlTimerCallback (timer=,
> timer_info=0x7fdedc0017
Op maandag 18 maart 2013 18:19:51 schreef Jiri Denemark:
> On Thu, Mar 14, 2013 at 20:01:16 +0100, AL13N wrote:
> > Op maandag 11 maart 2013 12:59:08 schreef Eric Blake:
> > > On 03/10/2013 09:25 AM, AL13N wrote:
> > > > regarding
> > > >
> > > > http://www.redhat.com/archives/libvir-list/2012-Dec
Op maandag 18 maart 2013 18:19:51 schreef Jiri Denemark:
> On Thu, Mar 14, 2013 at 20:01:16 +0100, AL13N wrote:
> > Op maandag 11 maart 2013 12:59:08 schreef Eric Blake:
> > > On 03/10/2013 09:25 AM, AL13N wrote:
> > > > regarding
> > > >
> > > > http://www.redhat.com/archives/libvir-list/2012-Dec
On Thu, Mar 14, 2013 at 20:01:16 +0100, AL13N wrote:
> Op maandag 11 maart 2013 12:59:08 schreef Eric Blake:
> > On 03/10/2013 09:25 AM, AL13N wrote:
> > > regarding
> > >
> > > http://www.redhat.com/archives/libvir-list/2012-December/msg01365.html
> > >
> > > and
> > >
> > > https://www.redhat.
Op maandag 11 maart 2013 12:59:08 schreef Eric Blake:
> On 03/10/2013 09:25 AM, AL13N wrote:
> > regarding
> >
> > http://www.redhat.com/archives/libvir-list/2012-December/msg01365.html
> >
> > and
> >
> > https://www.redhat.com/archives/libvir-list/2012-December/msg00935.html
>
> There have be
Op maandag 11 maart 2013 12:59:08 schreef Eric Blake:
> On 03/10/2013 09:25 AM, AL13N wrote:
> > regarding
> >
> > http://www.redhat.com/archives/libvir-list/2012-December/msg01365.html
> >
> > and
> >
> > https://www.redhat.com/archives/libvir-list/2012-December/msg00935.html
>
> There have be
Op maandag 11 maart 2013 12:59:08 schreef Eric Blake:
> On 03/10/2013 09:25 AM, AL13N wrote:
> > regarding
> >
> > http://www.redhat.com/archives/libvir-list/2012-December/msg01365.html
> >
> > and
> >
> > https://www.redhat.com/archives/libvir-list/2012-December/msg00935.html
>
> There have be
On 03/10/2013 09:25 AM, AL13N wrote:
> regarding
>
> http://www.redhat.com/archives/libvir-list/2012-December/msg01365.html
>
> and
>
> https://www.redhat.com/archives/libvir-list/2012-December/msg00935.html
There have been several fixes to shutdown since December; can you
reproduce the proble
regarding
http://www.redhat.com/archives/libvir-list/2012-December/msg01365.html
and
https://www.redhat.com/archives/libvir-list/2012-December/msg00935.html
This seems like the problem i'm having... is there a permanent solution for
this?
(i'm using libvirtd with XEN using libxl)
almost eve
On 01/02/2013 09:45 AM, Scott Sullivan wrote:
On 12/29/2012 04:09 AM, Michal Privoznik wrote:
On 28.12.2012 20:23, Scott Sullivan wrote:
I have just now received another SIGSEGV, with your patch applied.
Here's the info from the GDB session:
Detaching after fork from child process 11266.
201
On 12/29/2012 04:09 AM, Michal Privoznik wrote:
On 28.12.2012 20:23, Scott Sullivan wrote:
I have just now received another SIGSEGV, with your patch applied.
Here's the info from the GDB session:
Detaching after fork from child process 11266.
2012-12-28 18:56:53.261+: 29943: error : q
On 28.12.2012 20:23, Scott Sullivan wrote:
> I have just now received another SIGSEGV, with your patch applied.
>
> Here's the info from the GDB session:
>
> Detaching after fork from child process 11266.
> 2012-12-28 18:56:53.261+: 29943: error : qemuMonitorIO:614 :
> internal error End of
On 12/28/2012 01:31 PM, Scott Sullivan wrote:
On 12/28/2012 10:50 AM, Michal Privoznik wrote:
On 28.12.2012 14:24, Scott Sullivan wrote:
In case its useful, here's the 'bt' output from this session as well:
(gdb) bt
#0 qemuDomainObjBeginJobInternal (driver=0x7fffe401d740,
driver_locked=true,
On 12/28/2012 10:50 AM, Michal Privoznik wrote:
On 28.12.2012 14:24, Scott Sullivan wrote:
In case its useful, here's the 'bt' output from this session as well:
(gdb) bt
#0 qemuDomainObjBeginJobInternal (driver=0x7fffe401d740, driver_locked=true,
obj=0x7fff80001b00, job=QEMU_JOB_DESTROY,
On 28.12.2012 14:24, Scott Sullivan wrote:
> In case its useful, here's the 'bt' output from this session as well:
>
> (gdb) bt
> #0 qemuDomainObjBeginJobInternal (driver=0x7fffe401d740, driver_locked=true,
> obj=0x7fff80001b00, job=QEMU_JOB_DESTROY, asyncJob=QEMU_ASYNC_JOB_NONE) at
> qemu/qemu
In case its useful, here's the 'bt' output from this session as well:
(gdb) bt
#0 qemuDomainObjBeginJobInternal (driver=0x7fffe401d740,
driver_locked=true, obj=0x7fff80001b00, job=QEMU_JOB_DESTROY,
asyncJob=QEMU_ASYNC_JOB_NONE) at qemu/qemu_domain.c:768
#1 0x7fffeac2b223 in qemuDomainDest
### Libvirt version: ###
libvirt tagged v1.0.0 from git , with
f0e72b2f5c675f927d04545dc5095f9e5998f171 applied
### Problem: ###
Libvirtd segfaults
### Steps to reproduce: ###
This is difficult to reproduce; but appears to happen only when doing
'virsh destroys', and when they are ran in c
23 matches
Mail list logo