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

[Alexandre DERUMIER]

maybe:

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


at vm start:

-start with max memory
if min_balloon size specified, set balloon size to min_ballon.


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.



What do you think ?


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

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

I just check on a xenserver test server, they are 3 values in vm config for memory 

memory-static-max (memory) 
memory-dynamic-max (balloon max) 
memory-dynamic-min (balloon min) 



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

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


> >>We already have 2 memory related settings: 
> >> 
> >>memory: xxx (= maximum) 
> >>balloon: yyy (maybe we can use this as minimum?) 
> 
> I think that balloon value must be the current balloon value. 
> (if pvestatd ajust the balloon memory, we must update this value, 

>>why ? 

We can also pool the current balloon value with qmp. 

> and we 
> want to keepit when we do a live migration). 

>>sure, but live migration can also query actual value. 
Yes, indeed you are right 

> I would like also keep the possibility to set the balloon size manually. 

>>Why (can't see that on the citrix GUI)? 
Yes indeed, it's not part on citrix gui. (but I think that setting min=max can fix the balloon size) 


> Also we can start a a vm with 32GB, set the balloon at 8GB max for now, and 
> adjust max balloon value later, if workload change. 

>> So what does that mean (don’t get the conclusion)? 

I would like to be able to start with a max ballon size lower than max memory size. 
(I have some customers whos want to start at 8GB (and pay for 8GB), but in time, they would like to increase memory available up to 32GB) 


maybe: 
memory: xxx 
balloon: yyy (mininum), xxx(maximum). 

So I can set balloon minimum = maximum, if I want fix the balloon size ? 




----- 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 10:33:17 
Objet: RE: [pve-devel] pve-manager : expose balloon to gui 

> >>We already have 2 memory related settings: 
> >> 
> >>memory: xxx (= maximum) 
> >>balloon: yyy (maybe we can use this as minimum?) 
> 
> I think that balloon value must be the current balloon value. 
> (if pvestatd ajust the balloon memory, we must update this value, 

why ? 

> and we 
> want to keepit when we do a live migration). 

sure, but live migration can also query actual value. 

> I would like also keep the possibility to set the balloon size manually. 

Why (can't see that on the citrix GUI)? 

> Also we can start a a vm with 32GB, set the balloon at 8GB max for now, and 
> adjust max balloon value later, if workload change. 

So what does that mean (don’t get the conclusion)?