From: Harald Koenig <H.Koenig@science-computing.de>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Cc: Harald Koenig <koenig@science-computing.de>
Subject: Re: [Xen-users] "Memory squeeze in netback driver"
Date: Tue, 21 Nov 2006 16:29:02 +0100 [thread overview]
Message-ID: <20061121152902.GA17085@atuin.science-computing.de> (raw)
In-Reply-To: <907625E08839C4409CE5768403633E0B018E1652@sefsexmb1.amd.com>
Hi,
today my XEN server run into the same problem: many kernel messages in dom0
xen_net: Memory squeeze in netback driver.
printk: 4 messages suppressed.
and all 13 domU networks are dead.
this is a dual-dual-core-operon (4 CPUs) running SUSE 10.1 in dom0
(xen 3.0.2_09763-0.8 from SUSE) with 8GB ram and Broadcom BCM5704 Gigabit Ethernet
on Supermicro H8DA8.
is there any chance to avoid rebooting dom0 ?
is it possible to avoid this problem in the future ?
On Oct 19, Petersson, Mats wrote:
> dom0_mem shouldn't be added to the vmlinuz line, but to the xen.gz line
> - which I think is the reason your dom0 is showing 12GB. Not sure if
> that's got anything to do with the above problem tho'.
I don't think so because in my setup I'm passing dom0_mem to xen:
kernel /boot/xen.gz dom0_mem=500M com1=38400,8n1 console=vga,com1 sync_console
module /boot/vmlinuz-xen root=/dev/sda1 showopts console=ttyS0,38400 console=tty0
but checking the time stamps in syslog when those messages started continuesly
(there are some few "Memory squeeze in netback" events from time to time)
it looks like this might got triggered by the creation of a new domU
which caused the dom0 being shrinked from 500 MB to ~290 MB
(dom0-min-mem is 196). shortly after that, dom0 was reset to 500 MB.
here is a short histogram on the number of "Memory squeeze in netback driver"
messages per hour (with those "printk: XXX messages suppressed" added correctly)
day HH count
Nov 20 16 1
Nov 20 17 1
Nov 20 18 350
Nov 20 19 273
Nov 20 20 277
Nov 20 21 268
Nov 20 22 250
Nov 20 23 275
Nov 21 00 1195
Nov 21 01 3600
Nov 21 02 3600
Nov 21 03 3600
Nov 21 04 3595
Nov 21 05 3600
...
around 18 o'clock (6 pm;) the dom0 memory resize happend. looks like this
was an initial trigger for the problem.
the external connection got lost around 00:45 am this moring, which matches
the increase of those netback messages from about every 15 secs to every second.
do you need any more information ?
on xen-devel I found only two mails about "Memory squeeze in netback driver"
from Isaku Yamahata <yamahata@valinux.co.jp> with a patch which removes
that kernel printk():
Attachment #2: 9897:5fcebfab4e31_netback_autotranslate_mode.patch
# HG changeset patch
# User yamahata@valinux.co.jp
# Node ID 5fcebfab4e317f1db0b0379ac4be99d8cdb9b2b2
# Parent a19cc748469e99eae7f289f3beb03206982b9ba2
change semantics of grant transfers for vp guests so that the
operation automatically gets you a fresh page at the same
pseudo-physical address as Keir suggested.
PATCHNAME: netback_autotranslate_mode
any ideas or comments ?
thanks,
Harald Koenig
--
"I hope to die ___ _____
before I *have* to use Microsoft Word.", 0--,| /OOOOOOO\
Donald E. Knuth, 02-Oct-2001 in Tuebingen. <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig \/\/\/\/\/\/\/\/\/
science+computing ag // / \\ \
koenig@science-computing.de ^^^^^ ^^^^^
parent reply other threads:[~2006-11-21 15:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <907625E08839C4409CE5768403633E0B018E1652@sefsexmb1.amd.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061121152902.GA17085@atuin.science-computing.de \
--to=h.koenig@science-computing.de \
--cc=koenig@science-computing.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.