[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] how to change the memory size of a VM

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Jia Rao <rickenrao@xxxxxxxxx>
  • Date: Mon, 2 Nov 2009 15:42:19 -0500
  • Delivery-date: Mon, 02 Nov 2009 12:42:48 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=rjkgrclpLwE2540gxof2e1YjDuvyn36XnYS9sXQzQeJYIYhN0bViVgPjxirv1DpHeA JiaAMswEqqKoJmWgh/lu4NYQlF43AhZcqLFwtCyUjrPtB031zvzXtiKhtS+dBkP+PWqt MCUUUZAXMwieQfN7hxxBVlq/kZGS+mW3jBW50=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi all,

I am looking into a problem that when the memory size of a VM is changed which part of the original memory is taken away by xen.
For example, if I change the memory size of a VM from 2048MB --> 1024MB, how can I tell which are the 1024M byte that will be taken away (I do not want the xen to take the memory spaces that are caching useful data).

The command for memory size reconfiguration is "xm mem-set", so I looked the source code of xm.
It turned out to be the following python calls:

tools/python/xen/xm/main.py: setMemoryTarget(dom, mem_target)
tools/python/xen/xend/XendDomainInfo.py: setMemoryTarget:         self._safe_set_memory('memory_dynamic_min', target * MiB)
        self._safe_set_memory('memory_dynamic_max', target * MiB)
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.