[ovirt-users] Segmentation fault in libtcmalloc
Dan Kenigsberg
danken at redhat.com
Fri Nov 13 19:00:14 UTC 2015
On Fri, Nov 13, 2015 at 07:56:14AM +0000, Grundmann, Christian wrote:
> Hi,
> i am using "ovirt-node-iso-3.6-0.999.201510221942.el7.centos.iso" (is there something better to use?) fort he nodes, and have random crashes of VMs
> The dumps are always the Same
>
> gdb --batch /usr/libexec/qemu-kvm core.45902.1447199164.dump
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `/usr/libexec/qemu-kvm -name vmname -S -machine rhel6.5.0,accel=kvm,usb=o'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x00007f0c559c4353 in tcmalloc::ThreadCache::ReleaseToCentralCache(tcmalloc::ThreadCache::FreeList*, unsigned long, int) () from /lib64/libtcmalloc.so.4
>
>
> Didn't have the Problem with 3.5 el6 nodes, so don't no if ist centos7 or 3.6
Due to the low-leveled-ness of the problem, I'd guess it's a
qemu//lib64/libtcmalloc malloc bug, and not directly related to ovirt.
Please report the precise version of qemu,kernel,libvirt and
gperftools-libs to qemu-devel mailing list and the complete stack trace
and qemu command line, if possible.
More information about the Users
mailing list