On 08/17/2009 01:49 PM, Thomas Fjellstrom wrote:
One thing I found odd about kvm's ballooning is that it actually seems to change how much ram the guest has. I really didn't expect "free -m" to report that the guest only had 64M ram after I manually ballooned the ram. I was however expecting it just to free ram it wasn't using in the host. To me, it just doesn't seem to be the same thing. now it'll start swapping at 64M ram instead of just reallocating the ram it used to have.
You expectations aren't realistic. kvm never allocates the ram the guest doesn't use in the first place. Ballooning just the "free" memory is pointless since it's usually a very small amount.
It may be worthwhile for the guest to give up that memory voluntarily though.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
