Re: [Xen-API] Startup Memory for Guests

[George Shuklin <george.shuklin@xxxxxxxxx>]

All stuff around memory management around squeezed is slightly... not perfect.

After we've hit that problem (actually, in different way - to start with minimum and raise slowly) we've implement special field in our management system - start_memory.

Now VM start looking like this:

vm_dynamic_memory_range_set min=start_memory max=start_memory
vm_start
(normal regulation memory happens here - in case of pure-xapi solution it will be vm_dynamic_memory_range_set min=min, max=max)

Something like that. Here (sorry, Russian) some extended description for consumers of our service: http://habrahabr.ru/company/selectel/blog/180331/

I think squeezed is somehow outdated and need to expose more tunable variables to users.

(Main problem I really hate is that squeezed and xapi disallow change static-max on-the-fly, for example, for memory-hotplug memory grow).

On 31.08.2013 02:05, Rushikesh Jadhav wrote:

Hi list,

While using ballooning, I found that VM always uses its "target" memory as startup memory. Is it possible to change it to static max as startup memory ?

Basically I have hosts where I want VM to start with max possible memory and then shrink if there are other VMs trying to start. ÂIf the static-max is available then start/restart should use that. ÂIt will give better host utilization for me.

Any ideas how would I do that with help of XAPI ?

Thanks.

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api