group.of.nepali.translators team mailing list archive

[ChristianEhrhardt <1670659@xxxxxxxxxxxxxxxxxx>]

I agree, and in fact I've come to this error a few times in several crash reports and it always ended up with "sorry, config issue likely too few memory".
Please do mind that there were a few cases where this triggered without really being OOM.

For the option to be set - not only for performance, but also consideration of other related impact it should be enabled upstream and come down from there. That would make sure that coverage is high and also any part of the stack that might have developed tweaks/workarounds around it to adapt (lessons learned from the past).
If you really want you can just ask for comments there on switching the default - if the answers are enlightening we can link them here.

I highly appreciate that you wrote such a detailed analysis about it.

One more thing, if you know a simpler way to get from the crash dump to
the extracted messages e.g. a sial script for crash and only a few
commands along that would be great to be documented here as well. I
guess that would help everybody crossing that issue again to confirm if
in "their" case it actually was a qemu allocation issue.

** Also affects: libvirt (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: libvirt (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: libvirt (Ubuntu Zesty)
   Importance: Medium
     Assignee: Rafael David Tinoco (inaddy)
       Status: Confirmed

** Changed in: libvirt (Ubuntu Zesty)
       Status: Confirmed => Opinion

** Changed in: libvirt (Ubuntu Yakkety)
       Status: New => Won't Fix

** Changed in: libvirt (Ubuntu Xenial)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1670659

Title:
  Libvirt can crash on lack of memory when starting multiple instances

Status in libvirt package in Ubuntu:
  Opinion
Status in libvirt source package in Xenial:
  Won't Fix
Status in libvirt source package in Yakkety:
  Won't Fix
Status in libvirt source package in Zesty:
  Opinion

Bug description:
  This bug is just informative since I don't think the fix applies and
  I'll explain why.

  Description:    Ubuntu 16.04.2 LTS

  libvirt-bin          1.3.1-1ubuntu10.8    
  qemu-system-x86      1:2.5+dfsg-5ubuntu10.9  

  I was given a dump with the main thread's back trace like this:

  #0  0x00007f94529f1428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
  #1  0x00007f94529f302a in __GI_abort () at abort.c:89
  #2  0x00007f9452a337ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f9452b4c2e0 "*** Error in `%s': %s: 0x%s ***\n")
      at ../sysdeps/posix/libc_fatal.c:175
  #3  0x00007f9452a3ea5a in malloc_printerr (ar_ptr=0x3, ptr=<optimized out>, str=<optimized out>, action=3) at malloc.c:5004
  #4  _int_realloc (av=av@entry=0x7f9452d7fb20 <main_arena>, oldp=oldp@entry=0x55bf445eb9d0, oldsize=oldsize@entry=2912,
      nb=nb@entry=2848) at malloc.c:4250
  #5  0x00007f9452a3fc89 in __GI___libc_realloc (oldmem=0x55bf445eb9e0, bytes=bytes@entry=2839) at malloc.c:3043
  #6  0x00007f945340d2f3 in virReallocN (ptrptr=ptrptr@entry=0x7ffe2f31c0a0, size=size@entry=1, count=count@entry=2839,
      report=report@entry=false, domcode=domcode@entry=0, filename=filename@entry=0x0, funcname=0x0, linenr=0)
      at ../../../src/util/viralloc.c:245
  #7  0x00007f942c00c119 in qemuProcessReadLog (msg=0x7ffe2f31c098, logCtxt=<optimized out>) at ../../../src/qemu/qemu_process.c:1684
  #8  qemuProcessReportLogError (logCtxt=<optimized out>, msgprefix=0x7f942c095548 "early end of file from monitor, possible problem")
      at ../../../src/qemu/qemu_process.c:1696
  #9  0x00007f942c0223fc in qemuMonitorIO (watch=watch@entry=107, fd=<optimized out>, events=<optimized out>, events@entry=13,
      opaque=opaque@entry=0x7f94000ab3b0) at ../../../src/qemu/qemu_monitor.c:718
  #10 0x00007f945342b393 in virEventPollDispatchHandles (fds=<optimized out>, nfds=<optimized out>)
      at ../../../src/util/vireventpoll.c:509
  #11 virEventPollRunOnce () at ../../../src/util/vireventpoll.c:658
  #12 0x00007f9453429c01 in virEventRunDefaultImpl () at ../../../src/util/virevent.c:314
  #13 0x00007f9453575b4d in virNetDaemonRun (dmn=0x55bf445c28e0) at ../../../src/rpc/virnetdaemon.c:701
  #14 0x000055bf43449407 in main (argc=<optimized out>, argv=<optimized out>) at ../../../daemon/libvirtd.c:1577

  And the analysis goes in the comments...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1670659/+subscriptions