RE: [Xen-users] Why top command doesn't return correct memory amount (xentop see my 3gb..) ?

["Petersson, Mats" <Mats.Petersson@xxxxxxx>]

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Sébastien CRAMATTE
> Sent: 13 October 2006 00:15
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Why top command doesn't return correct 
> memory amount (xentop see my 3gb..) ?
> 
> Hello
> 
> Why top command doesn't return correct memory amount (xentop see my
> 3gb..) ?
> I've compiled my kernel with  4GB high mem support ...

Because TOP and XENTOP show different things... Xentop shows how much memory is 
used/available in all domains. 

Top on any particular machine (such as domain0) will show the amount of memory 
available in THAT virtual machine. Dom0 is a virtual machine just like any 
other domain in xen - it's only special because it can access hardware and has 
privileges to create/kill other domains etc. 

If you compare the amoutn of memory in Dom0 in Xentop: 2050268 with the amoutn 
shown by top 2050048, you can see that they aren't very far apart.

--
Mats

> 
> #xentop
> xentop - 01:16:21   Xen 3.0.2-3
> 6 domains: 1 running, 5 blocked, 0 paused, 0 crashed, 0 
> dying, 0 shutdown
> Mem: 3144744k total, 2947952k used, 196792k free    CPUs: 2 @ 3000MHz
>       NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k)
> MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) SSID
>   Domain-0 -----r        162    0.0    2050268   65.2   no limit      
> n/a     2    8     7605    61335    0
>       ldap --b---         36    0.0     200512    6.4     200704      
> 6.4     1    1     2423    74941    0
>       mail --b---         65    0.0     200448    6.4     200704      
> 6.4     1    1     5519    46455    0
>         ns --b---        245    0.0     130900    4.2     131072      
> 4.2     1    1     8263    59350    0
>       snmp --b---        548    0.0     200488    6.4     200704      
> 6.4     1    1    13894    48256    0
>        www --b---         34    0.0     130924    4.2     131072      
> 4.2     1    1     1140    59911    0
> 
> #top
> top - 01:16:44 up 12:21,  1 user,  load average: 0.00, 0.00, 0.00
> Tasks:  70 total,   2 running,  66 sleeping,   2 stopped,   0 zombie
> Cpu(s):  0.0% us,  0.0% sy,  0.0% ni, 99.5% id,  0.5% wa,  
> 0.0% hi,  0.0% si
> Mem:   2050048k total,   227024k used,  1823024k free,    
> 33464k buffers
> Swap:        0k total,        0k used,        0k free,    
> 57044k cached
> 
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>     1 root      16   0  1580  516  452 S  0.0  0.0   0:00.97 init
>     2 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 
> migration/0
>     3 root      34  19     0    0    0 S  0.0  0.0   0:00.00 
> ksoftirqd/0
>     4 root      RT   0     0    0    0 S  0.0  0.0   0:00.03 
> migration/1
>     5 root      34  19     0    0    0 S  0.0  0.0   0:00.00 
> ksoftirqd/1
>     6 root      10  -5     0    0    0 S  0.0  0.0   0:00.54 events/0
>     7 root      10  -5     0    0    0 S  0.0  0.0   0:00.35 events/1
>     8 root      11  -5     0    0    0 S  0.0  0.0   0:00.00 khelper
> 
> 
> it's little bite anoying for dom0 snmp monitoring ...
> any ideas or solution ?
> 
> regars
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 
> 



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