For example, lets says you are running several guests, and would like
to
start yet another one for a while - but have no free memory left.
We have another solution for it that will soon be pushed into the
kernel:
It is the balloon driver solution.
Each guest runs a balloon driver, when
For example, lets says you are running several guests, and would
like
to
start yet another one for a while - but have no free memory left.
We have another solution for it that will soon be pushed into the
kernel:
It is the balloon driver solution.
Each guest runs a balloon driver, when
On Thursday 05 April 2007, Dor Laor wrote:
For example, lets says you are running several guests, and would
like
to
start yet another one for a while - but have no free memory left.
We have another solution for it that will soon be pushed into the
kernel:
It is the balloon driver
Arnd Bergmann wrote:
Another driver you might want to look at is the Xen balloon driver:
http://81.161.245.2/lxr/http/source/linux-2.6-xen-
sparse/drivers/xen/balloon/balloon.c
The s390 driver is probably a better example though. One thing the
Xen one got wrong is that its interface requires
On Thursday 05 April 2007, Dor Laor wrote:
Currently the only memory-over-commit mechanism is the balloon.
In the future we will add all the wise spectrum of host demand pages,
shared pages, etc.
Ok, just as another hint: you should definitely take a look at
pfault_interrupt() in
Arnd Bergmann wrote:
On Thursday 05 April 2007, Dor Laor wrote:
Currently the only memory-over-commit mechanism is the balloon.
In the future we will add all the wise spectrum of host demand pages,
shared pages, etc.
Ok, just as another hint: you should definitely take a look at
On Thursday 05 April 2007, Avi Kivity wrote:
arch/s390/mm/extmem.c has another very interesting concept, though the
hcall interfaces used there are not as flexible as they should be in
kvm. It's basically about mapping host files into the guest real address
space, e.g. for shared memory
On Thursday 05 April 2007, Avi Kivity wrote:
arch/s390/mm/extmem.c has another very interesting concept, though
the
hcall interfaces used there are not as flexible as they should be
in
kvm. It's basically about mapping host files into the guest real
address
space, e.g. for shared memory
Does KVM allow something like memory hotplug for its guests?
For example, lets says you are running several guests, and would like to
start yet another one for a while - but have no free memory left.
Obviously, your guests are so important that you don't want to stop them
- so you simply