[Xen-changelog] [xen-unstable] [XEND] Currently a domain's maxmem value is being set with the memory value

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kfraser@xxxxxxxxxxxxxxxxxxxxx
# Node ID 3c74df4f33f067af1844e11df9388d1c1758cfb6
# Parent  5014fd2b5c5aab37e83ceaddb1a65b8f50d1f5f7
[XEND] Currently a domain's maxmem value is being set with the memory value
even if the user specifies maxmem in config.  This patch uses maxmem
value to set maxmem instead of memory.

Signed-off-by: Ryan Harper <ryanh@xxxxxxxxxx>
---
 tools/python/xen/xend/XendDomainInfo.py |    4 +++-
 1 files changed, 3 insertions(+), 1 deletion(-)

diff -r 5014fd2b5c5a -r 3c74df4f33f0 tools/python/xen/xend/XendDomainInfo.py
--- a/tools/python/xen/xend/XendDomainInfo.py   Mon Jul 10 15:38:49 2006 +0100
+++ b/tools/python/xen/xend/XendDomainInfo.py   Mon Jul 10 15:57:56 2006 +0100
@@ -1302,9 +1302,11 @@ class XendDomainInfo:
                     cpu = [ int( cpus[v % len(cpus)] ) ]
                     xc.vcpu_setaffinity(self.domid, v, cpu)
 
+            # set domain maxmem in KiB
+            xc.domain_setmaxmem(self.domid, self.info['maxmem'] * 1024)
+
             m = self.image.getDomainMemory(self.info['memory'] * 1024)
             balloon.free(m)
-            xc.domain_setmaxmem(self.domid, m)
 
             init_reservation = self.info['memory'] * 1024
             if os.uname()[4] == 'ia64':

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog