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

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

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

Hi,

No, I don't know for details. 
AFAIK, an upper limit of maxmem value is under 2 TiB. 
I consulted a description of the following changeset. 

 http://xenbits.xensource.com/xen-unstable.hg?rev/9647be59212d

But, current maxmem value of Domain-0 is 4 TiB - 1 MiB as follows. 

# xm list --long Domain-0 | grep maxmem
    (maxmem 4194303)

Best regards,
 Kan

>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

<Prev in Thread] Current Thread [Next in Thread>