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

[Alexandre DERUMIER]

>>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, and we want to keepit when we do a live migration).
I would like also keep the possibility to set the balloon size manually.

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.


maybe:

memory: xxxx
balloon: xxxx,automin=xxxx,automax=xxxx

?


----- 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 09:39:47 
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?) 


> -----Original Message----- 
> From: Alexandre DERUMIER [mailto:aderumier at odiso.com] 
> Sent: Donnerstag, 06. Dezember 2012 09:19 
> To: Dietmar Maurer 
> Cc: pve-devel at pve.proxmox.com 
> Subject: Re: [pve-devel] pve-manager : expose balloon to gui 
> 
> 
> >>Another way (that citrix xenserver use) it to specify manually a range (min- 
> max) for balloon memory (which is safe for the workload of the vm). 
> Like this: 
> http://blog.virtualyoungtech.com/wp- 
> content/uploads/2012/01/XenDynamicMemory01.jpg 
> 
> 
> 
> 
> 
> 
> 
> 
> ----- 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 09:09:37 
> Objet: Re: [pve-devel] pve-manager : expose balloon to gui 
> 
> >>The MOM Ballooning Policy does not look very complex. But if we can't 
> >>implement it inside qemu, we can still use pvestatd. 
> 
> >>But we first need to know if/how we can get stats from the guest? 
> 
> If we want to reduce memory 100% safely, I think we need to get stats. 
> But balloon stats seem to give "free_memory", without memory used as 
> buffer in guest. 
> (And as Linux try to use all free memory for buffer, I'm not sure that 
> free_memory will be huge) 
> 
> I we want to add memory, I can be done if host have enough memory. 
> 
> Another way (that citrix xenserver use) it to specify manually a range (min- 
> max) for balloon memory (which is safe for the workload of the vm). 
> Then the daemon (pvestatd), can adjust balloon in this range. 
> 
> 
> 
> 
> ----- 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 08:56:26 
> Objet: RE: [pve-devel] pve-manager : expose balloon to gui 
> 
> > >>But for me this only makes sense if we do not need a daemon inside 
> > >>the guest, and qemu can handle ballooning itself (no 'momd'). 
> > 
> > I'm not a big fan of automatic memory management (because it's a 
> > complex thing), but why not. 
> > I'm not sure a single qemu process can manage it easily, because it 
> > need to known if you can reclaim space from another qemu,or if host 
> > have enough memory free. 
> 
> The MOM Ballooning Policy does not look very complex. But if we can't 
> implement it inside qemu, we can still use pvestatd. 
> 
> But we first need to know if/how we can get stats from the guest?