[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>
This commit is contained in:
kfraser@localhost.localdomain committed 2006-07-10 15:57:56 +01:00
1 parent 6b900ffb50
commit 1a1f70afb8
1 file changed
+3 -1
+3 -1
View File
@@ -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':
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.