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

[Xen-devel] [PATCH] set maxmem bugfix

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: aq <aquynh@xxxxxxxxx>
  • Date: Fri, 15 Jul 2005 17:13:16 +0900
  • Delivery-date: Fri, 15 Jul 2005 08:11:59 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=bkWYkUeg8SaNexh6tEpJXn91sazUecr90eLSSQUG/Vrb45pFkgrgZj+1liGKNVl2gHuALPM76/Fmyj05IPidwxFCrCBaMp/xVOf6e1z5jaYAeWU6ud2oTteD9f00Uyj9Wquc1Ogd902VLUSZsKbCm/+N89F8iLlAYWgfUPmFjyk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Recently some people complain that they cannot set the maxmem for
domU. The problem is that some code wrongly treat dom.max_memkb as in
byte unit, instead of KB unit. This patch fixs the problem.

Signed-off-by: Nguyen Anh Quynh <aquynh@xxxxxxxxx>

$ diffstat maxmem.patch 
 xc_domain.c     |    2 +-
 xc_linux_save.c |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Attachment: maxmem.patch
Description: Binary data

Xen-devel mailing list



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