On Wed, Jan 11, 2012 at 10:58:54AM +0000, Guido Trotter wrote: > Not exactly. > > - There is no such thing as "min" at run time
Hmm. Right now (in 2.6) not, but this would have been the value that Xen (or KVM) is allowed to auto-balloon-down the instance. But I might be wrong indeed and there's no such memory. Hrmm… Then would the oper_mem (running_mem) be the minimum for the hypervisor? I think I misjudged a bit these, I'll have to rethink and see how all the thinks (capacity, auto-ballooning, etc.) will work. > - As for "max" it cannot be modified without a reboot. > > So it's all true except the last sentence: we just want a way to modify > oper_ram, live. (there is no sense in doing it non-live) Ack. Whether we keep oper_ram (for consistency with instance list) or we rename it to running_ram it's for decision. thanks! iustin > On Jan 11, 2012 11:02 AM, "Iustin Pop" <ius...@google.com> wrote: > > > On Tue, Jan 10, 2012 at 06:28:51PM +0000, Guido Trotter wrote: > > > We still need --running-mem: this is meant for ballooning without > > changing > > > min and max, which are the only values we currently save. > > > > Guid, can you confirm this is correct? > > > > - we have min/max mem, which are config values > > - we have oper_ram, which is the current running memory (between > > min/max) > > - currently gnt-instance modify only allows changing min/max _in the > > config_ > > - we want to be able to modify min/max at runtime and also oper_ram at > > runtime > > > > iustin > > > > > On Jan 10, 2012 3:47 PM, "Michael Hanselmann" <han...@google.com> wrote: > > > > > > > Am 10. Januar 2012 12:29 schrieb Iustin Pop <ius...@google.com>: > > > > > Hmm, right. But then I'd make it a different key (e.g. running-mem or > > > > > such), but still in instance modify. > > > > > > > > Or add a new parameter “--live” to apply the changes right away. > > > > > > > > Michael > > > > > >
