On Mon, Apr 22, 2019 at 04:02:28PM +0200, Hans van Kranenburg wrote: > On 4/22/19 1:10 AM, Elliott Mitchell wrote: > > There is plenty of free memory for creating additional VMs (perhaps too > > much, and that confused Xen?), so this is really puzzling that memory is > > being ballooned away from Dom0. At this point I plan after the next > > restart to double the allocation for Dom0 and see whether Dom0 is able > > to last more than a week. > > Weird. Can you log memory stats over time, so that you can see when it > happens, and correlate it to other events?
At this point there is only one real pattern I've noticed: Always `smartd` was the process which triggered the kernel OOM-killer. Originally I was attributing this to `smartd` doing some large memory allocation during its night-time tasks (which I would attribute to perhaps `smartd` not being that well written). Yet now, I never saw anything else trigger the OOM-killer and I'm now willing to speculate some I/O operation `smartd` was doing triggers a bug in Xen. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445