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

[Dietmar Maurer]

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

I think we should use 'memory hotplug' for that - maybe it will arrive soon ;-)

Using ballooning for that is dangerous, because you can easily run out of memory
at VM startup (before balloon driver wroks).

Anyways, I guess it is easy to add such hack.

I would really like to start implementing some automatic ballooning inside
pvestatd. To do that we need first need to evaluate the balloon stat patches (qemu-devel list).
Are you interested in that task?