<div dir="ltr">Hi Laine,<div><br></div><div>I can confirm that the v2 patch worked to resolve my problem. Thanks all for your kind assistance!</div><div><br></div><div>Will</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 11, 2015 at 2:48 AM, Laine Stump <span dir="ltr"><<a href="mailto:laine@laine.org" target="_blank">laine@laine.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 08/11/2015 02:13 AM, Laine Stump wrote:<br>
> On 08/11/2015 02:06 AM, Laine Stump wrote:<br>
>> On 08/11/2015 01:30 AM, Ján Tomko wrote:<br>
>>> On Mon, Aug 10, 2015 at 11:21:47PM -0400, Willard Dennis wrote:<br>
>>>> Compiled libvirt 1.2.18 on Ubuntu 12.04.5 (installed over 12.04 libvirt-bin<br>
>>>> 0.9.9 package files); when I try to start libvirtd, I get the following<br>
>>>> error / backtrace:<br>
>>>><br>
>>>> $ sudo /usr/sbin/libvirtd<br>
>>>> *** stack smashing detected ***: /usr/sbin/libvirtd terminated<br>
>>>> ======= Backtrace: =========<br>
>>>> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f02fe6d3e57]<br>
>>>> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f02fe6d3e20]<br>
>>>> /usr/lib/libvirt.so.0(+0xaa359)[0x7f02fec4f359]<br>
>>>> /usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so(+0x99fe)[0x7f02f1fc59fe]<br>
>>>> /usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so(+0xa672)[0x7f02f1fc6672]<br>
>>>> /usr/lib/libvirt.so.0(virStateInitialize+0xaf)[0x7f02fed1cd2f]<br>
>>>> /usr/sbin/libvirtd(+0x17d80)[0x7f02ff98dd80]<br>
>>>> /usr/lib/libvirt.so.0(+0xd25d2)[0x7f02fec775d2]<br>
>>>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f02fe98fe9a]<br>
>>>> /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f02fe6bd38d]<br>
>>>><br>
>>>> Not sure if this may be a bug with 1.2.18, or a fault with my<br>
>>>> configure/compile/install process; please advise...<br>
>>> This has been reported last week:<br>
>>> <a href="https://www.redhat.com/archives/libvir-list/2015-August/msg00163.html" rel="noreferrer" target="_blank">https://www.redhat.com/archives/libvir-list/2015-August/msg00163.html</a><br>
>>> And here is the patch proposed to fix it, waiting on review:<br>
>>> <a href="https://www.redhat.com/archives/libvir-list/2015-August/msg00263.html" rel="noreferrer" target="_blank">https://www.redhat.com/archives/libvir-list/2015-August/msg00263.html</a><br>
>> Willard - If you're able to build libvirt and test that patch, it would<br>
>> be greatly appreciated.<br>
> Ah, wait. Actually I'm fairly certain that the patch that Jan refers to<br>
> will *not* fix the problem. The patch that I'd like to see tested is the<br>
> one that I posted just a few hours ago:<br>
><br>
>   <a href="https://www.redhat.com/archives/libvir-list/2015-August/msg00382.html" rel="noreferrer" target="_blank">https://www.redhat.com/archives/libvir-list/2015-August/msg00382.html</a><br>
><br>
<br>
</div></div>Or even better, the V2 of that patch which I just posted as a reply to<br>
the original:<br>
<br>
<a href="https://www.redhat.com/archives/libvir-list/2015-August/msg00392.html" rel="noreferrer" target="_blank">https://www.redhat.com/archives/libvir-list/2015-August/msg00392.html</a><br>
</blockquote></div><br></div>