Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-17 Thread Stefano Stabellini
On Fri, 17 Feb 2017, Jan Beulich wrote: > >>> On 16.02.17 at 19:38, wrote: > > On Thu, 16 Feb 2017, Jan Beulich wrote: > >> >>> On 16.02.17 at 16:23, wrote: > >> On 14.02.17 at 15:56, wrote: > >> >> On Fri, Feb 10, 2017 at 02:54:23AM -0700, Jan Beulich wrote: > >> >>> Not so far. It appears

Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-16 Thread Jan Beulich
>>> On 16.02.17 at 19:38, wrote: > On Thu, 16 Feb 2017, Jan Beulich wrote: >> >>> On 16.02.17 at 16:23, wrote: >> On 14.02.17 at 15:56, wrote: >> >> On Fri, Feb 10, 2017 at 02:54:23AM -0700, Jan Beulich wrote: >> >>> Not so far. It appears to happen when grub clears the screen >> >>> before

Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-16 Thread Stefano Stabellini
On Thu, 16 Feb 2017, Jan Beulich wrote: > >>> On 16.02.17 at 16:23, wrote: > On 14.02.17 at 15:56, wrote: > >> On Fri, Feb 10, 2017 at 02:54:23AM -0700, Jan Beulich wrote: > >>> Not so far. It appears to happen when grub clears the screen > >>> before displaying its graphical menu, so I'd ra

Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-16 Thread Jan Beulich
>>> On 16.02.17 at 16:23, wrote: On 14.02.17 at 15:56, wrote: >> On Fri, Feb 10, 2017 at 02:54:23AM -0700, Jan Beulich wrote: >>> Not so far. It appears to happen when grub clears the screen >>> before displaying its graphical menu, so I'd rather suspect an issue >>> with a graphics related

Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-16 Thread Jan Beulich
>>> On 14.02.17 at 15:56, wrote: > On Fri, Feb 10, 2017 at 02:54:23AM -0700, Jan Beulich wrote: >> Not so far. It appears to happen when grub clears the screen >> before displaying its graphical menu, so I'd rather suspect an issue >> with a graphics related change (the one you pointed out isn't).

Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-15 Thread Jan Beulich
>>> On 14.02.17 at 15:56, wrote: > I tried to reproduce this, by limiting the amount of memory available to > qemu using cgroups, but about 44MB of memory is enough to boot a guest > (tried Ubuntu and Debian). > > How much memory did qemu try to use? According to kernel: Out of memory: Kill pro

Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-14 Thread Anthony PERARD
On Fri, Feb 10, 2017 at 02:54:23AM -0700, Jan Beulich wrote: > >>> On 09.02.17 at 23:24, wrote: > > On Thu, 9 Feb 2017, Jan Beulich wrote: > >> the recent qemuu update results in the produced binary triggering the > >> OOM killer on the first system I tried the updated code on. Is there > >> anyth

Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-10 Thread Jan Beulich
>>> On 09.02.17 at 23:24, wrote: > On Thu, 9 Feb 2017, Jan Beulich wrote: >> the recent qemuu update results in the produced binary triggering the >> OOM killer on the first system I tried the updated code on. Is there >> anything known in this area? Are there any hints as to finding out >> what i

Re: [Xen-devel] qemu-upstream triggering OOM killer

2017-02-09 Thread Stefano Stabellini
CC'ing Anthony On Thu, 9 Feb 2017, Jan Beulich wrote: > Stefano, > > the recent qemuu update results in the produced binary triggering the > OOM killer on the first system I tried the updated code on. Is there > anything known in this area? Are there any hints as to finding out > what is going wr

[Xen-devel] qemu-upstream triggering OOM killer

2017-02-09 Thread Jan Beulich
Stefano, the recent qemuu update results in the produced binary triggering the OOM killer on the first system I tried the updated code on. Is there anything known in this area? Are there any hints as to finding out what is going wrong? Thanks, Jan ___