On Wed, Dec 24, 2008 at 01:33:06AM +0100, Emre Erenoglu wrote:
Hi Daniel,
On Sun, Dec 21, 2008 at 6:15 PM, Daniel P. Berrange <berrange@redhat.com>wrote:
However, I still have the crash in the dmesg output, as before, errors
like:
sysfs: duplicate filename '0' can not be created
------------[ cut here -------------
WARNING: at fs/sysfs/dir.c:424 sysfs_add_one+0x34/0xa6() ... Pid: 2616, comm: libvirtd Tainted: P 2.6.25.20-113 #1 ... *kobject_add_internal failed for 0 with -EEXIST, don't try to register things with the same name in the same directory.*
Any of these messages in the dmesg output are kernel problems, not libvirt problems. The process listing you show about indicates that libvirtd itself is running, and has not crashed.
Daniel
Using eclipse and gdb, I've traced the problem until this line in source code. Source code filename lxc_container.c, line 654, this function:
cpid = clone(lxcContainerDummyChild, childStack, flags, NULL);
is crashing something inside my kernel, which results in the messages that I've sent previously in this thread.
Then I recommend you report a bug against the kernel with your OS distribution's bug tracker. I've no idea why its crashing your kernel, but the code works fine on vanilla Fedora kernels. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|