On Mon, Jul 19, 2010 at 09:34:10AM +0200, Guido Günther wrote: > Hi Adam, > On Sun, Jul 18, 2010 at 05:34:20PM -0500, Adam Majer wrote: > > Package: libvirt > > Version: 0.8.2-1 > > Severity: normal > > > > I'm getting segfaults trying to start lxc container, > > > > # virsh -c lxc:/// version > > Compiled against library: libvir 0.8.2 > > Using library: libvir 0.8.2 > > Using API: LXC 0.8.2 > > Running hypervisor: LXC 2.6.34 > > > > # dmesg > > [2239291.304216] device veth0 entered promiscuous mode > > [2239291.311094] ADDRCONF(NETDEV_UP): veth0: link is not ready > > [2239291.360445] libvirt_lxc[2155] general protection ip:b7571071 > > sp:bf83cbe8 error:0 in libc-2.10.2.so[b7501000+141000] > > [2239291.386751] br0: port 12(veth0) entering disabled state > > [2239291.402318] device veth0 left promiscuous mode > > [2239291.402373] br0: port 12(veth0) entering disabled state > > Thanks for you report. Could you provide a backtrace using the > libvirt0-dbg package?
I would if it was straight forward :) Do you have know where in the libvirtd source code it calls the libvirt_lxc executable? I can't simply set gdb to `fork-and-follow=child` because then it just ends after libvirtd forks `ip` command. I've also set `ulimit -c unlimited` and then got libvirt_lxc to crash, yet, no core file is dumped. :/ - Adam -- Adam Majer [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
