Tomasz Chmielewski wrote:
BTW, is it possible to "balloon" to a bigger amount of memory that what was available when the guest started?
No. The guest won't have its data structures set up to handle the extra memory.
Or is it only possible to "shrink" and "grow" within initial memory available to the guest, but never "grow" beyond it?
Right. One workaround is to start the guest with more memory than you need and immediately balloon it down. Hopefully we'll have memory hotplug one day so it can be fixed properly.
-- 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
