debuggers.hg

changeset 10695:3c74df4f33f0

find changesets by author, revision, files, or words in the commit message
[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@us.ibm.com>
author kfraser@localhost.localdomain
date Mon Jul 10 15:57:56 2006 +0100 (2006-07-10)
parents 5014fd2b5c5a
children b875c036839f
files tools/python/xen/xend/XendDomainInfo.py
line diff
     1.1 --- a/tools/python/xen/xend/XendDomainInfo.py	Mon Jul 10 15:38:49 2006 +0100
     1.2 +++ b/tools/python/xen/xend/XendDomainInfo.py	Mon Jul 10 15:57:56 2006 +0100
     1.3 @@ -1302,9 +1302,11 @@ class XendDomainInfo:
     1.4                      cpu = [ int( cpus[v % len(cpus)] ) ]
     1.5                      xc.vcpu_setaffinity(self.domid, v, cpu)
     1.6  
     1.7 +            # set domain maxmem in KiB
     1.8 +            xc.domain_setmaxmem(self.domid, self.info['maxmem'] * 1024)
     1.9 +
    1.10              m = self.image.getDomainMemory(self.info['memory'] * 1024)
    1.11              balloon.free(m)
    1.12 -            xc.domain_setmaxmem(self.domid, m)
    1.13  
    1.14              init_reservation = self.info['memory'] * 1024
    1.15              if os.uname()[4] == 'ia64':