[xenpreview-dev] dom0-min-mem parameter in xend-config.sxp

[Krysan, Susan]

No, I've done some further testing and applying the Xen security update
did not affect the problem.  Instead, it appears to be related to high
host memory (128GB).  I opened bug 225481 for this problem.  

Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
 
-----Original Message-----
From: Puthiyaparambil, Aravindh 
Sent: Friday, December 01, 2006 5:31 PM
To: Charles Coffing; xenpreview-dev at forge.novell.com; Krysan, Susan
Cc: Subrahmanian, Raj; McAfee, Tommie M; Vessey, Bruce A; Carb, Brian A
Subject: RE: [xenpreview-dev] dom0-min-mem parameter in xend-config.sxp

Charles,

There was a patch in the SLES10 Xen which imposed a hard lower limit
(196Mb + 5%) on ballooning. I remember Ky Srinivasan saying that this
would be in the SLES10 Xen even though it is not part of unstable. 

Sue, please correct if I am wrong... I think with the gold master we did
not see this issue. But after applying the first set of SUSE updates we
started to see the hang. So was this hard limit removed?

> We're assuming the admin knows what he's doing, but it sounds like you
> want some extra vendor-specified limits to keep things in a
supportable
> configuration?  If we wanted to do such a thing, I suppose the
dom0-min-
> mem setting could always be checked; if the admin really wanted to
over-
> ride this (at his own peril) he could edit the config file before
doing a
> lower mem-set.
> 
> Any comments for or against this approach?

I submitted such a patch but it was not accepted.
http://www.nabble.com/-PATCH--Make-%22xm-mem-set%22-be-lower-bound-on-do
mX-min-mem-tf1608742.html#a4513746

Aravindh