On Wed, Jan 19, 2011 at 07:54:52AM -0700, Eric Blake wrote: > On 01/18/2011 05:28 PM, Justin Clift wrote: > > This completes the man page updates required for BZ # 622534: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=622534 > > =item B<setmaxmem> I<domain-id> B<kilobytes> > > > > -Change the maximum memory allocation limit in the guest domain. This should > > -not change the current memory use. The memory limit is specified in > > -kilobytes. > > +Change the maximum memory allocation limit for an active guest domain. > > I'm a bit confused here. Doesn't maximum memory allocation only take > effect at domain boot? So it seems like something you can't change at > runtime, and if a change is made to an active domain, it only affects > the configured version and the next boot of the domain rather than > having an immediate effect. But I haven't played closely with > setmaxmem, so I could be wrong. In theory we could change maxmem at runtime, if the guest truely supported memory hotplug, instead of simply ballooning. No hypervisor or guest in existance really does that yet. So 'max mem' should be considered a boot time only tunable at this time. Daniel -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list