Javier Guerra schrieb:
On Mon, Mar 30, 2009 at 10:15 AM, Tomasz Chmielewski <[email protected]> wrote:
Still, if there is free memory on host, why not use it for cache?
because it's best used on the guest;
It is correct, but not realistic from the administrative point of view.
Let's say you have several KVM hosts, each with 16 GB RAM.
Guests can come and go - so you give them only as much memory as they
need (more or less).
In other words, normally, you don't create the first guest with 16 GB
RAM assigned. Upon creation of the second guest 2 hours later, you don't
stop guest 1, just to start both guests with 8 GB RAM a while later. And
so on. And so on, stopping and starting a whole bunch of guests until
each of them has 512 MB RAM.
No, not all guests support ballooning.
But for those which support ballooning, the easiest way to implement it
would be to write a user-space daemon I guess.
so, not
cacheing already-cached data, it's free to cache other more important
things, or to keep more of the VMs memory on RAM.
Correct - if the host knew what the guest already cached, the host could
use RAM for other things.
Anyway, there are still more pressing issues than that ;)
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
