FS#57156 - [libvirt] libvirtd from libvirt-3.10.0-1 segfaulting

Attached to Project: Community Packages
Opened by brent saner (sanerb) - Friday, 19 January 2018, 12:27 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 27 January 2018, 16:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Rebischke (Shibumi)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
libvirt-3.10.0-1 is giving segfaults during normal operation (namely, as soon as the daemon is started):

dmesg snippet (this is spanned to dmesg frequently):

[ 1301.795506] libvirtd[3484]: segfault at 10 ip 00007f1d877773b8 sp 00007f1d65b659f0 error 4 in libvirt_driver_storage.so[7f1d87767000+2f000]
[ 1304.081417] libvirtd[3754]: segfault at 10 ip 00007fa6c63123b8 sp 00007fa6a8e509f0 error 4 in libvirt_driver_storage.so[7fa6c6302000+2f000]
[ 1306.318038] libvirtd[4039]: segfault at 10 ip 00007fe41fbcc3b8 sp 00007fe3f63669f0 error 4 in libvirt_driver_storage.so[7fe41fbbc000+2f000]


journal output (also spammed frequently) is attached. (too large to attach inline here)


i've confirmed it seems to be isolated to 3.10.0; i downgraded back to 3.9.0-2 via ALA and it's working fine now, no segfaults.
   libvirt.journald.log (19.4 KiB)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 27 January 2018, 16:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  libvirt 4.0.0-1
Comment by brent saner (sanerb) - Friday, 19 January 2018, 12:30 GMT
heh. s/spanned/spammed/ obviously, whoops.
Comment by loqs (loqs) - Friday, 19 January 2018, 17:05 GMT
https://github.com/libvirt/libvirt/commit/2d07f1f0ebd44b0348daa61afa0de34f3f838c22 ?
Comment by brent saner (sanerb) - Friday, 19 January 2018, 17:11 GMT
definitely seems to be in line with what i'm seeing, loqs, looking at the RHEL bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1522682) referenced in the commit.

and i think that might be the same conditions, too. looks like the fix is probably in 4.0.0-rc1 onwards
Comment by Christian Rebischke (Shibumi) - Saturday, 27 January 2018, 02:58 GMT
I hope the update on 4.0.0 will fix this issue. Stay tuned!
Comment by Christian Rebischke (Shibumi) - Saturday, 27 January 2018, 03:05 GMT
Please checkout 4.0.0-1 and give me feedback if this bug is fixed.
Comment by brent saner (sanerb) - Saturday, 27 January 2018, 11:34 GMT
starts up fine with no errors in dmesg, created, destroyed guests, all without error! :)

Loading...