Re: [Xen-users] dom0 - oom-killer - memory leak somewhere ?

["Likarpenkov Alexander" <al@xxxxxxxxxxxxxxx>]

In my servers now 16g memory. Until such time as did restrictions dom0_mem = 
512M and less, the amount of memory capacity increased. After a 512 MB 
limit - I have a situation where the physical memory is occupied, and 
completely empty swap. In this balooning - I do not cut off.
Basic postulate stable operation - Dom0 should have a minimum of software, 
and most importantly do not use the internet through virbr0. For 
distribution network is used as a gateway DomU. And bridges are created 
manually at boot time.
LSC> On Thu, Jan 26, 2012 at 11:09:09AM -0800, John Weekes wrote:
??>> Were you ever able to determine what was using the memory? I had
??>> several machines at the same location all enter this state this
??>> morning at the same time, and I can't find any clues as to what's
??>> exhausting the memory, just as you couldn't. The circumstances suggest
??>> that some sort of attack or network event was involved, but I'm not
??>> seeing significant traffic levels. One of the machines was brand new
??>> (very latest Xen 4.1, very latest xen/next-2.6.32) and had no activity
??>> otherwise. It's very puzzling.

LSC> Huh.   This happened to me way back in the day, but it hasn't happened
LSC> for years.

LSC> I completely disabled balooning in the dom0.   dom0_mem=1024m.
LSC> for good measure, (enable-dom0-ballooning no) in xend-config.sxp.
LSC> I give the thing a gig because, hey, ram is cheap.  I give the thing a
LSC> two gigs of swap because, hey, disk is even cheaper, but it hasn't
LSC> been used.  Back in the day, I'd give it ten, because I thought that I
LSC> could login and check things out; Nope.

LSC> But yeah;  my experience?  the dom0 balooning (and really, balooning
LSC> in general) is trouble.  I mean, if you want to baloon guests, that's
LSC> fine; if they go wonky you reboot them.   but rebooting a dom0 is so
LSC> much pain that it's got to have fixed ram.

LSC> Nearly all of my problems of this nature were a result of accidentally
LSC> causing the dom0 to baloon.

LSC> and, in your case, I'd setup a logging screen session or something and
LSC> run 'top' sorted by memory use on the offending hosts.   that should
LSC> give you some idea of what's eating all the ram if it really is a
LSC> runaway process. and check your logs for the dom0 balooning.   It's on
LSC> a serial console, right? 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users