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
The balloon driver allows guests to express to the hypervisor how much
memory they require. The balloon driver allows the host to efficiently
allocate memory to the guest and allow free memory to be allocated to
other guests and processes.
Guests using the balloon driver can mark sections of
- 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
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
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:
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
