On Sat, Dec 20, 2008 at 12:25 AM, Emre Erenoglu <erenoglu@xxxxxxxxx> wrote:
My suspections were correct. The dnsmasq does not have anything to do with the crash. I installed the dnsmasq package and it works fine:Hi Daniel,
I'm very surprised. dnsmasq is not listed in the dependencies of libvirt as far as I know. I was guessing that it's a "nice to have" package, to enable DHCP IP distriPid: 2616, comm: libvirtd Tainted: P 2.6.25.20-113 #1
bution to guests. But even if it doesn't exist, I shall normally be able to assign static IP addresses manually to my guests.
So if the system crashes due to dnsmasq, I would call it a bug instead.
Nevertheless, I'll try to compile this package for our distro and see what happens.
I'll keep you posted, thanks again a lot for your interest.
2616 pts/1 S+ 0:00 /usr/sbin/libvirtd
2637 pts/1 S+ 0:00 dnsmasq --keep-in-foreground --strict-order --bind-interfaces --pid-file --conf-file --listen-address 192.168.122.1 --except-interface lo --dhcp-leasefile=/var/lib/libvirt/dhcp-d
2637 pts/1 S+ 0:00 dnsmasq --keep-in-foreground --strict-order --bind-interfaces --pid-file --conf-file --listen-address 192.168.122.1 --except-interface lo --dhcp-leasefile=/var/lib/libvirt/dhcp-d
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.
...
Pid: 2616, comm: libvirtd Tainted: P 2.6.25.20-113 #1
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.
...
Pid: 2616, comm: libvirtd Tainted: P 2.6.25.20-113 #1
The DEBUG output shows in the last lines:
DEBUG: util.c: virExec (dnsmasq --keep-in-foreground --strict-order --bind-interfaces --pid-file --conf-file --listen-address 192.168.122.1 --except-interface lo --dhcp-leasefile=/var/lib/libvirt/dhcp-default.leases --dhcp-range 192.168.122.2,192.168.122.254)
DEBUG: lxc_container.c: lxcContainerAvailable (clone call returned Cannot allocate memory, container support is not enabled)
DEBUG: lxc_container.c: lxcContainerAvailable (clone call returned Cannot allocate memory, container support is not enabled)
I still suspect the compiler flags. Any suggestions? What about this last DEBUG message regarding the container support?
Thanks a lot & Best Regards,
Emre
-- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list