[Xen-bugs] [Bug 1113] New: when issuing a sub command of xm, 'mem-set', the size is limited

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1113

           Summary: when issuing a sub command of xm, 'mem-set', the size is
                    limited
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: heedae.poem@xxxxxxxxx


I got a host machine whose memory size was 6G. And create one new guest machine
for test with xen api 1.0. And all the features seemed very successful.
However, I found out some problem about a sub command 'mem-set' of xm.
Whenever I gave mem-set command one value exceeded 2G(or 2048M) as the last
argument(one new i wanted), I got consistant error said that
'Error: Invalid argument.
Usage: xm mem-set <Domain> <Mem>'.
Absolutly, the element 'memory_static_max', I set at the time of the creation ,
of that machine was larger than 2G. So I didn't think the error due to that.

But I could make and run guest machine with whatever size, only less than the
usable of the physical machine, which I had set it at the time of the creation
with configuration files, even if the size of the memory of the guest machine
exceeded 2G. It went without saying that it was ok to set one less than 2G,
irrespective of when I set it.

So I tracked the detailed error, thanks to the xm constructed in python.
Then I caught the detailed error 'long int exceeds XML-RPC limits'
I guessed it would be due to the limit of the size of integer on XML RPC
protocol.The value 2G would exceed the limit.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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