On 13/01/2011, at 8:54 AM, Eric Blake wrote: > On 01/12/2011 02:24 PM, Justin Clift wrote: >> Addresses BZ # 622534: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=622534 >> --- >> tools/virsh.pod | 28 ++++++++++++++++++---------- >> 1 files changed, 18 insertions(+), 10 deletions(-) <snip> > Do we need extra text talking about rounding and/or rejection if the > hypervisor can't support a memory limit with that small of a granularity > (for example, Matthias recently posted patches regarding esx only having > megabyte granularity). Hows this for the setmem virsh text? setmem domain-id new-allocation Immediately change the current memory allocation for an active guest domain. The new-allocation value is in kilobytes, and will be rejected if the hypervisor can't support the given memory allocation. For vSphere/ESX, the new-allocation value must be a multiple of megabytes (ie. 2048 for 2GB), otherwise the hypervisor will reject it. For Xen, you can only adjust the memory of a running domain if the domain is paravirtualized or running the PV balloon driver. Note, this command only works on active guest domains. To change the memory allocation for an inactive guest domain, use the virsh edit command to update the XML <memory> element. -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list