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

[Alexandre DERUMIER]

>>Note: Inside qemu balloon size is something else. 
Yes, Indeed, qmp balloon set the target memory and not the balloon size

memory :2000MB, 
qmp baloon (500MB).
memory : 500MB,  balloon size: 1500MB 



> -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. 

Yes, indeed no change from actual implementation.



>>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.

I Agree with that.

>>After that, we set available memory to something between yyy and xxx dynamically.
>>
>>Would that work for you?

I would like to specify an optionnal upper limit for ballooned memory, lower than the total memory.

Because we don't have memory hotplug yet, so I would like start the vm with an higher memory size, and increase the max ballon size limit in time.(like fake hotplug)



----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Jeudi 6 Décembre 2012 13:02:28 
Objet: RE: [pve-devel] pve-manager : expose balloon to gui 

> 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?