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

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 14.02.17 at 15:56, <anthony.perard@xxxxxxxxxx> 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 process 9018 (qemu-system-i38) score 291 or 
sacrifice child
kernel: Killed process 9018 (qemu-system-i38) total-vm:4525776kB, 
anon-rss:3732084kB, file-rss:4kB, shmem-rss:0kB
kernel: oom_reaper: reaped process 9018 (qemu-system-i38), now 
anon-rss:3720556kB, file-rss:0kB, shmem-rss:0kB

well over 4Gb.

> What guest did you try to boot?

SLES11 SP4, but I've also just now tried Win7, which demonstrates
the same behavior. I'd like to note that the host is an older distro,
so I can't exclude there being something that qemu now simply
expects to be newer (I find upstream qemu to be notoriously bad
in ensuring backwards compatibility, but usually this surfaces as
build problems).

> What the xl configuration?

name="sles11-hvm64"
description="None"
uuid="5b537ac6-aa31-9c3e-9c7c-f0360a19acd5"
memory=2048
maxmem=3072
vcpus=8
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
keymap="en-us"

builder="hvm"
boot="c"
disk=[ 'file:/var/lib/xen/images/sles11-hvm64/disk0.raw,hda,w', ]
vif=[ 'mac=00:16:3e:33:39:71,bridge=br0,model=rtl8139,type=vif', ]

stdvga=0
vnc=1
vncunused=1
viridian=0
acpi=1
pae=1

serial="pty"

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel