/srv/irclogs.ubuntu.com/2018/11/15/#ubuntu-x.txt

michael-vbHello again.  I am here with a different issue: when I start a virtual machine in VirtualBox with vmgfx emulation and 3D enabled, my whole (Ubuntu 18.10) system hangs.  With tjaalton's updated X server packages, but I doubt they are related.10:34
michael-vbI see some OOM killer entries in the system log, sometimes for the VM process, sometimes for Xwayland, but neither of those processes looks like it is OOM-ing the system based on the memory usage reported in the log entries.10:34
michael-vbSo wondering if anyone has an idea how I can debug this, or who else I could poke.  The system is a Thinkpad T470 with HD Graphics 620.10:34
tjaaltonmichael-vb: is it the host which hangs, or client?10:46
michael-vbThe host.10:46
michael-vbOh yes, and it happens with X or Wayland session, no matter.10:50
tjaaltoncould be a bug in i915, hard to tell10:53
michael-vbThat was also my first guess.10:54
michael-vbWhen the OOM killer hits the VM process the system recovers.  When it hits Xwayland I can at least switch VTs.10:55
tjaaltonok so it is oom related10:56
tjaaltonlimit the display ram in vbox?10:56
michael-vbThe whole VM process is comfortably under host system RAM.10:58
michael-vbThough it might be interesting to try increasing the VM VRAM.10:58
michael-vbAs I said, the OOM logs suggested that VBox was not using a lot of RAM.10:58
michael-vbOr Xwayland for that matter.10:59
tjaaltonbut sounds like they'd balloon and oom kills them10:59
tjaaltonor something11:00
michael-vbRight, but it prints the amount of RAM they were using at kill time into the log.11:00
michael-vbI am guessing that i915 starts swallowing system RAM and that the OOM killer then starts going for small-ish processes.  It has also hit as and cpp.  But that is just a guess so far.11:10
tjaaltontry #intel-gfx11:11
michael-vbThanks.11:11

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!