Hi all,
How can I manage automatically memory ballooning under a kvm host (C5.6 and future C6)?? For example if I define a kvm guest to boot up with 512MB of RAM and I have configured 1GB as a maximum memory for this guest, how can I allocate this memory when guest will need it??
And the opposite question, can memory balloon be deallocated?? And is it possible to do this automatically or is an error to do this??
Thanks.
carlopmart wrote on 04/23/2011 05:04 PM: ...
How can I manage automatically memory ballooning under a kvm host (C5.6 and future C6)??
Looks like you got an answer to your nearly identical post on rhelv6-list:
https://www.redhat.com/archives/rhelv6-list/2011-April/msg00055.html
Phil
On 04/25/2011 05:03 PM, Phil Schaffner wrote:
carlopmart wrote on 04/23/2011 05:04 PM: ...
How can I manage automatically memory ballooning under a kvm host(C5.6 and future C6)??
Looks like you got an answer to your nearly identical post on rhelv6-list:
https://www.redhat.com/archives/rhelv6-list/2011-April/msg00055.html
Phil
yes, but doesn't answer my question ...
----- Original Message ----- | Hi all, | | How can I manage automatically memory ballooning under a kvm host | (C5.6 and future C6)?? For example if I define a kvm guest to boot up | with 512MB of RAM and I have configured 1GB as a maximum memory for | this | guest, how can I allocate this memory when guest will need it?? | | And the opposite question, can memory balloon be deallocated?? And is | it possible to do this automatically or is an error to do this?? | | Thanks. | | -- | CL Martinez | carlopmart {at} gmail {d0t} com | _______________________________________________ | CentOS-virt mailing list | CentOS-virt@centos.org | http://lists.centos.org/mailman/listinfo/centos-virt
No you cannot do it automatically. It must be scripted and reboots are required. Under any 5.x branch it is simply not possible as not all information needed to be provided may be available. Can't remember where I read that, but it was quite recent. Check the RH documentation
And the opposite question, can memory balloon be deallocated?? And is it possible to do this automatically or is an error to do this??
I think your understanding of ballooning may be backwards. The purpose of the balloon driver is to give the host system a way of recovering memory from the guest when the demands on the host's physical memory exceed the amount available. The balloon inflates within the guests forcing them to swap or take other memory management measures. When the pressure on the host eases the balloon deflates automatically.
-
carlopmart -
Drew -
James A. Peltier -
Phil Schaffner