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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670659
Title:
Libvirt can crash on lack of memory when starting multiple instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1670659/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
