libvirtd crashed with SIGSEGV in _getbit()

[APolihron]

I get this ereor after the last update!

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libvirt-daemon 3.6.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
Date: Wed Aug 16 23:05:38 2017
ExecutablePath: /usr/sbin/libvirtd
InstallationDate: Installed on 2017-08-08 (8 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170808)
ProcAttrCurrent: /usr/sbin/libvirtd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed root=UUID=03910234-d984-4e33-a345-7cf681d9ca3a ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fd9520c5752 <numa_bitmask_isbitset+2>: cmp (%rdi),%rax
 PC (0x7fd9520c5752) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libvirt
StacktraceTop:
 numa_bitmask_isbitset () from /usr/lib/x86_64-linux-gnu/libnuma.so.1
 virNumaNodeIsAvailable () from /usr/lib/x86_64-linux-gnu/libvirt.so.0
 virHostMemGetInfo () from /usr/lib/x86_64-linux-gnu/libvirt.so.0
 virNumaGetPageInfo () from /usr/lib/x86_64-linux-gnu/libvirt.so.0
 virNumaGetPages () from /usr/lib/x86_64-linux-gnu/libvirt.so.0
Title: libvirtd crashed with SIGSEGV in numa_bitmask_isbitset()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 _getbit (n=0, bmp=0x0) at libnuma.c:152
 numa_bitmask_isbitset (bmp=0x0, i=i@entry=0) at libnuma.c:153
 virNumaNodeIsAvailable (node=node@entry=0) at ../../../src/util/virnuma.c:396
 virHostMemGetInfo (mem=mem@entry=0x7fd92eac0918, freeMem=freeMem@entry=0x7fd92eac0920) at ../../../src/util/virhostmem.c:736
 virNumaGetPageInfo (node=-1, page_size=4, huge_page_sum=0, page_avail=0x7fd928154868, page_free=0x7fd9281419e8) at ../../../src/util/virnuma.c:662

[Christian Ehrhardt  (paelzer)]

Hi,
very interesting - thanks for the report Apolihron!

I'd like to recreate to debug and search for a fix.
Since in all my tests I haven't seen it yet it is likely dependent on your setup.
The numa related functions indicate an area but we might need to know more what exactly you are doing.

Might I ask for:
1. your guest xml
2. when does this happen - guest start, running a while, running a special load in guest, ...?
3. You host system setup, especially in regard to numa (maybe attach a /proc/zoneinfo)?

[Launchpad Janitor (janitor)]

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]