Compiled libvirt 1.2.18 on Ubuntu 12.04.5 (installed over 12.04 libvirt-bin 0.9.9 package files); when I try to start libvirtd, I get the following error / backtrace: $ sudo /usr/sbin/libvirtd *** stack smashing detected ***: /usr/sbin/libvirtd terminated ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f02fe6d3e57] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f02fe6d3e20] /usr/lib/libvirt.so.0(+0xaa359)[0x7f02fec4f359] /usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so(+0x99fe)[0x7f02f1fc59fe] /usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so(+0xa672)[0x7f02f1fc6672] /usr/lib/libvirt.so.0(virStateInitialize+0xaf)[0x7f02fed1cd2f] /usr/sbin/libvirtd(+0x17d80)[0x7f02ff98dd80] /usr/lib/libvirt.so.0(+0xd25d2)[0x7f02fec775d2] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f02fe98fe9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f02fe6bd38d] Not sure if this may be a bug with 1.2.18, or a fault with my configure/compile/install process; please advise...

On 08/11/2015 01:30 AM, Ján Tomko wrote: > On Mon, Aug 10, 2015 at 11:21:47PM -0400, Willard Dennis wrote: >> Compiled libvirt 1.2.18 on Ubuntu 12.04.5 (installed over 12.04 libvirt-bin >> 0.9.9 package files); when I try to start libvirtd, I get the following >> error / backtrace: >> >> $ sudo /usr/sbin/libvirtd >> *** stack smashing detected ***: /usr/sbin/libvirtd terminated >> ======= Backtrace: ========= >> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f02fe6d3e57] >> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f02fe6d3e20] >> /usr/lib/libvirt.so.0(+0xaa359)[0x7f02fec4f359] >> /usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so(+0x99fe)[0x7f02f1fc59fe] >> /usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so(+0xa672)[0x7f02f1fc6672] >> /usr/lib/libvirt.so.0(virStateInitialize+0xaf)[0x7f02fed1cd2f] >> /usr/sbin/libvirtd(+0x17d80)[0x7f02ff98dd80] >> /usr/lib/libvirt.so.0(+0xd25d2)[0x7f02fec775d2] >> /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f02fe98fe9a] >> /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f02fe6bd38d] >> >> Not sure if this may be a bug with 1.2.18, or a fault with my >> configure/compile/install process; please advise... > This has been reported last week: > https://www.redhat.com/archives/libvir-list/2015-August/msg00163.html > And here is the patch proposed to fix it, waiting on review: > https://www.redhat.com/archives/libvir-list/2015-August/msg00263.html Willard - If you're able to build libvirt and test that patch, it would be greatly appreciated.

On 08/11/2015 02:13 AM, Laine Stump wrote: > On 08/11/2015 02:06 AM, Laine Stump wrote: >> On 08/11/2015 01:30 AM, Ján Tomko wrote: >>> On Mon, Aug 10, 2015 at 11:21:47PM -0400, Willard Dennis wrote: >>>> Compiled libvirt 1.2.18 on Ubuntu 12.04.5 (installed over 12.04 libvirt-bin >>>> 0.9.9 package files); when I try to start libvirtd, I get the following >>>> error / backtrace: >>>> >>>> $ sudo /usr/sbin/libvirtd >>>> *** stack smashing detected ***: /usr/sbin/libvirtd terminated >>>> ======= Backtrace: ========= >>>> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f02fe6d3e57] >>>> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f02fe6d3e20] >>>> /usr/lib/libvirt.so.0(+0xaa359)[0x7f02fec4f359] >>>> /usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so(+0x99fe)[0x7f02f1fc59fe] >>>> /usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so(+0xa672)[0x7f02f1fc6672] >>>> /usr/lib/libvirt.so.0(virStateInitialize+0xaf)[0x7f02fed1cd2f] >>>> /usr/sbin/libvirtd(+0x17d80)[0x7f02ff98dd80] >>>> /usr/lib/libvirt.so.0(+0xd25d2)[0x7f02fec775d2] >>>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f02fe98fe9a] >>>> /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f02fe6bd38d] >>>> >>>> Not sure if this may be a bug with 1.2.18, or a fault with my >>>> configure/compile/install process; please advise... >>> This has been reported last week: >>> https://www.redhat.com/archives/libvir-list/2015-August/msg00163.html >>> And here is the patch proposed to fix it, waiting on review: >>> https://www.redhat.com/archives/libvir-list/2015-August/msg00263.html >> Willard - If you're able to build libvirt and test that patch, it would >> be greatly appreciated. > Ah, wait. Actually I'm fairly certain that the patch that Jan refers to > will *not* fix the problem. The patch that I'd like to see tested is the > one that I posted just a few hours ago: > > https://www.redhat.com/archives/libvir-list/2015-August/msg00382.html > Or even better, the V2 of that patch which I just posted as a reply to the original: https://www.redhat.com/archives/libvir-list/2015-August/msg00392.html