[pve-devel] pve-manager : expose balloon to gui

[Dietmar Maurer]

> maybe:
> 
> memory:xxx (max_memory)
> balloon:yyy (min_balloon ), optionnal zzz (max_balloon)

I don't really understand why we need a max_balloon value, because

max_balloon == memory size

> at vm start:
> 
> -start with max memory
> if min_balloon size specified, set balloon size to min_ballon.

we start as we start now, no need to change that.
 
> then pvestatd:
> 
> try to grow balloon size for each vm (need some algo to balance free mem)
> up to the max_memory  or max_ballon if specified.

grow/shrink balloon size - what do we talk about here. What is balloon size
exactly? From man 'vz.conf':

balloon: integer (16 - N)
        Amount of target RAM for the VM in MB.

Note: Inside qemu balloon size is something else.

To summarize, we have the following setting:

memory: xxx
balloon: yyy 

We start the VM with -mem 'xxx' and set available memory to 'yyy' (using ballooning).
So 'yyy' is the minimum available memory inside the VM.

After that, we set available memory to something between yyy and xxx dynamically.

Would that work for you?