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@jp.fujitsu.com>
Best regards,
Kan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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@jp.fujitsu.com>:> 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@jp.fujitsu.com> > > Best regards, > Kan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>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@jp.fujitsu.com>: > >> 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@jp.fujitsu.com> >> >> Best regards, >> Kan >>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel