Your message dated Wed, 21 Dec 2011 01:07:16 +0800
with message-id <[email protected]>
and subject line There's no issue, just user not using Xen correctly, so
closing.
has caused the Debian Bug report #640500,
regarding xen-hypervisor-4.0-amd64: xend invokes oomkiller and reboots machine
when creating DomU's
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
640500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640500
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xen-hypervisor-4.0-amd64
Version: 4.0.1-2
Severity: normal
Tags: upstream
When creating Xen DomU's, at some point xend invokes the oom-killer and
the entire machine restarts:
Sep 5 12:04:59 arbiter kernel: [259697.101212] __ratelimit: 136
callbacks suppressed
Sep 5 12:04:59 arbiter kernel: [259697.101218] xend invoked oom-killer:
gfp_mask=0x200da, order=0, oom_adj=0
Sep 5 12:04:59 arbiter kernel: [259697.101225] xend cpuset=/
mems_allowed=0
Sep 5 12:04:59 arbiter kernel: [259697.101230] Pid: 1841, comm: xend
Not tainted 2.6.32-5-xen-amd64 #1
Sep 5 12:06:23 arbiter kernel: imklog 4.6.4, log source = /proc/kmsg
started.
Sep 5 12:06:23 arbiter rsyslogd: [origin software="rsyslogd"
swVersion="4.6.4" x-pid="1409" x-info="http://www.rsyslog.com";]
(re)start
Sep 5 12:06:23 arbiter kernel: [ 0.000000] Initializing cgroup
subsys cpuset
xm info says the machine has 10231 MB of RAM. These are the VMs that
normally run:
Name ID Mem VCPUs State Time(s)
Domain-0 0 2177 1 r----- 127.1
one 1 1536 2 r----- 192.4
two 2 512 1 -b---- 2.7
three 3 1024 1 -b---- 188.6
four 4 512 1 -b---- 12.7
five 5 2048 2 -b---- 151.7
six 6 1024 2 r----- 64.9
seven 7 1024 2 -b---- 65.9
eight 8 1024 2 -b---- 100.7
That means 8704 MB of memory is used.
Over the last couple of days, I've experienced that when creating two
VM's with 512 MB RAM, the oom-killer is invoked. This should not happen
because Dom0 can shrink and because the machine should not restart when
it is out of memory.
This is a production Xen host, which is becomming a liability, because
it's so unpredictable.
Current Dom0 kernel: Linux arbiter 2.6.32-5-xen-amd64
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
xen-hypervisor-4.0-amd64 depends on no packages.
Versions of packages xen-hypervisor-4.0-amd64 recommends:
ii xen-utils-4.0 4.0.1-2 XEN administrative tools
Versions of packages xen-hypervisor-4.0-amd64 suggests:
pn xen-docs-4.0 <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
--- End Message ---
