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

[Charles Coffing]

I guess no one ever responded to this?

The dom0-min-mem setting only controls automatically-triggered ballooning (such as when creating a VM.)  Explicit requests, like your "xm mem-set" example, aren't limited by this setting.

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?


>>> On Wed, Nov 15, 2006 at  9:00 AM, in message
<EF8D308BE33AF54D8934DF26520252D30350458C at USTR-EXCH5.na.uis.unisys.com>,
"Krysan, Susan" <KRYSANS at unisys.com> wrote: 
> We boot our 128gb ES7000/one with dom0_mem=512M because without it, it
> takes a while for dom0 to balloon down from 128gb when creating larger
> domUs.  I would like to prevent users from ballooning dom0 down any
> lower than 512, so I have set the value of dom0- min- mem to 512 and
> rebooted.  When I do xm mem- set 0 256, the system starts to balloon down
> (as seen using xm top) and then it freezes and becomes unusable,
> requiring a reboot.  Shouldn't the dom0- min- mem value prevent dom0 from
> attempting to balloon down to 256 when xm command is used?  Or does it
> only control the minimum value for dom0 when the kernel determines it
> needs to balloon?
> 
>  
> 
> Thanks,
> 
> Sue Krysan
> 
> Linux Systems Group
> 
> Unisys Corporation
> 
>  
> 
>