WARNING - OLD ARCHIVES

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/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-devel] [PATCH] Fix xm mem-max command

from [weiming] [Permanent Link][Original]
To: "Masaki Kanno" <kanno.masaki@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Fix xm mem-max command
From: weiming <zephyr.zhao@xxxxxxxxx>
Date: Tue, 26 Feb 2008 08:30:06 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 26 Feb 2008 05:30:31 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=OfqtXayp14TNNKzUPHB2YA8VOUB1kAWQDw4DoiB5SBw=; b=oEKUltmrDjyUABggPeWDhTdEZ5jZ3CVEuRFarGvb5To8xp3IV0b4HTTwMa64kSkAmn9ZvWfFWI5SWarSifgAGkKFtJdagnjld2VUYIw+Y44Gsbz6i/pMNvjqPjBmwWL4ELvPH+rULWmLwi36s2tCoIy3dxnO8EZqo3DvN4AwZl0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=o9OEc5xOr5R4UstyVwXiiKB8KREa1dwobEO/KKqPcm1j0KcT1hp3hK/acQSzWiGzRuaB05ogerc8mqtTchrP/0OApS7nhBDnYJ7mjq5u3keDhcxcVYzEGaN0AVEUE1pgkKGW6LjwGn9ty5TqhdSP0gsm1pviKrb+dXbEOYKspyU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <9EC878685A7964kanno.masaki@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <9EC878685A7964kanno.masaki@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I got similar problems with these scripts on the range of int.
Do you know how to solve them radically?

weiming

2008/2/26 Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>:
Hi,

When I gave 2 TiB or more to xm mem-max command, I saw the following
error message.  But the maxmem value was changed.

# xm list --long vm1 | grep maxmem
   (maxmem 256)
# xm mem-max vm1 2097152
Error: long int too large to convert to int
Usage: xm mem-max <Domain> <Mem>

Set the maximum amount reservation for a domain.
# xm list --long vm1 | grep maxmem
   (maxmem 2097152)


This patch reverts the maxmem value to the previous maxmem value when
the error occurs.

# xm list --long vm1 | grep maxmem
   (maxmem 256)
# xm mem-max vm1 2097152
Error: long int too large to convert to int
Usage: xm mem-max <Domain> <Mem>

Set the maximum amount reservation for a domain.
# xm list --long vm1 | grep maxmem
   (maxmem 256)

Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>

Best regards,
 Kan


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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-devel] [PATCH] Fix abusive use of xce_handle as FD, Samuel Thibault
Next by Date:  [Xen-devel] [PATCH] minios: add PVFB support, Samuel Thibault
Previous by Thread:  [Xen-devel] [PATCH] Fix xm mem-max command, Masaki Kanno
Next by Thread:  Re: [Xen-devel] [PATCH] Fix xm mem-max command, Masaki Kanno
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy