This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] how to change the memory size of a VM
From: Jia Rao <rickenrao@xxxxxxxxx>
Date: Mon, 2 Nov 2009 15:42:19 -0500
Delivery-date: Mon, 02 Nov 2009 12:42:48 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=P1WL2Z1miyi8r6e+A+40gfQoDXimnNnjHkxboS2+eMI=; b=QH9RYN/LD4kxQF5hQEXyTenwe+Vom1bSC1/pzNLrSuxC/yRoT8aMh553ZmW0zAXJzH Iw9zwijuT5ECcsdGKeBh1faTAPX4fUEXpUui4dlYO1TtcyKbRPWMB3YLVegoXjsd0nY/ m7oDVyHtYp3Z/hqiaF1YUkGhG5VtMJYkRJP84=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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