<div dir="ltr"><div>Thanks Guys </div>
<div> </div>
<div>really apprecite your quick responses.</div>
<div>( Dennis was right in tellin me about PAE since my system is 64 bit and if I do run yum install kernel-PAE there is nothing found.)</div>
<div> </div>
<div>actually i found something more as i was figuring my issue out.</div>
<div> </div>
<div>when I do a top i see the following</div>
<div>---------------</div>
<div> </div>
<div>Tasks: 285 total, 1 running, 284 sleeping, 0 stopped, 0 zombie<br>Cpu(s): 0.0%us, 0.0%sy, 0.0%ni, 99.8%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st<br>Mem: 33554432k total, 15430836k used, 18123596k free, 323176k buffers<br>
Swap: 2819396k total, 0k used, 2819396k free, 13860960k cached</div>
<div> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND </div>
<div>---------------</div>
<div> </div>
<div>when I run cat /proc/meminfo i see</div>
<div> </div>
<div>----MemTotal: 33554432 kB<br>MemFree: 18123588 kB<br>Buffers: 323192 kB<br>Cached: 13860992 kB<br>SwapCached: 0 kB<br>Active: 9601264 kB<br>Inactive: 4643904 kB<br>HighTotal: 0 kB<br>
HighFree: 0 kB<br>LowTotal: 33554432 kB<br>LowFree: 18123588 kB<br>SwapTotal: 2819396 kB<br>SwapFree: 2819396 kB<br>Dirty: 8 kB<br>Writeback: 0 kB<br>AnonPages: 60972 kB<br>
Mapped: 12528 kB<br>Slab: 360860 kB<br>PageTables: 18444 kB<br>NFS_Unstable: 0 kB<br>Bounce: 0 kB<br>CommitLimit: 19596612 kB<br>Committed_AS: 394740 kB<br>VmallocTotal: 34359738367 kB<br>
VmallocUsed: 3304 kB<br>VmallocChunk: 34359733919 kB</div>
<div>------------</div>
<div> </div>
<div>actually I had run the above 2 command and found the memory was 32gb</div>
<div>but as dennis said when I run the command </div>
<div>xm info</div>
<div>----------------------</div>
<div>[root@hypervisor2 ~]# xm info<br>host : hypervisor2<br>release : 2.6.18-194.32.1.el5xen<br>version : #1 SMP Wed Jan 5 18:44:24 EST 2011<br>machine : x86_64<br>
nr_cpus : 16<br>nr_nodes : 1<br>sockets_per_node : 2<br>cores_per_socket : 4<br>threads_per_core : 2<br>cpu_mhz : 2527<br>hw_caps : bfebfbff:28100800:00000000:00000140:009ce3bd:00000000:00000001<br>
total_memory : 65527<br>free_memory : 22989<br>node_to_cpu : node0:0-15<br>xen_major : 3<br>xen_minor : 1<br>xen_extra : .2-194.32.1.el5<br>xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 <br>
xen_pagesize : 4096<br>platform_params : virt_start=0xffff800000000000<br>xen_changeset : unavailable<br>cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)<br>cc_compile_by : mockbuild<br>
cc_compile_domain : <a href="http://centos.org">centos.org</a><br>cc_compile_date : Wed Jan 5 17:43:03 EST 2011<br>xend_config_format : 2</div>
<div>--------------------</div>
<div>and then I ran xm top i see</div>
<div> </div>
<div>-------------</div>
<div> </div>
<div>5 domains: 1 running, 4 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown<br>Mem: 67099744k total, 43558844k used, 23540900k free CPUs: 16 @ 2527MHz<br> NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD<br>
_WR SSID<br> Domain-0 -----r 8401 2.4 33554688 50.0 no limit n/a 16 4 1892 16848120 0 0 0<br> 0 0<br> sepmback --b--- 9758 2.6 2105220 3.1 4210688 6.3 4 1 0 0 1 0 0<br>
0 0<br>winserver2 --b--- 5758 0.9 1056644 1.6 4210688 6.3 1 1 0 0 1 0 0<br> 0 0<br>wsusserver --b--- 25812 11.4 3256196 4.9 8404992 12.5 4 1 0 0 1 0 0<br>
0 0<br> zimbra --b--- 26183 7.8 2105220 3.1 4210688 6.3 4 1 0 16 1 0 0<br> 0 0<br>----------------------</div>
<div> </div>
<div>so the above 2 command show me 64gb</div>
<div> </div>
<div>Now I m confused ..</div>
<div> </div>
<div>Is my Centos XEN server actually using the 64 bit ...</div>
<div>and which command actually show me the right memory status</div>
<div> </div>
<div> </div>
<div>apprecite once again and thnaks</div>
<div> </div>
<div>regards</div>
<div> </div>
<div>sylvan</div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Fri, Aug 26, 2011 at 3:29 PM, Dennis Jacobfeuerborn <span dir="ltr"><<a href="mailto:dennisml@conversis.de">dennisml@conversis.de</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On 08/26/2011 12:51 PM, benedict dcunha wrote:<br>> Thanks Leonard,<br>> Thanks for the immedite reply . apprecite.<br>> actually many post s say the PAE kernel required for addressing more than 4<br>
> gb ram . but since my server already detects 32 gb ram , detecting 64 also<br>> should not be an issue..<br><br></div>"many posts say" a lot of things. Either these posts are specifically<br>talking about 32bit systems or they are wrong.<br>
With a 32bit integer you can only address 4gb of ram so a hack was devised<br>to make it possible go beyond that limit called PAE.<br>Since with 64bit you no longer have that problem PAE doesn't exist on a<br>64bit system.<br>
<br><a href="http://en.wikipedia.org/wiki/Physical_Address_Extension" target="_blank">http://en.wikipedia.org/wiki/Physical_Address_Extension</a><br><br>> but just wondering why??.<br><br>No idea but it has nothing to do with PAE. Can you post the output of "xm<br>
info"?<br><br>Regards,<br><font color="#888888"> Dennis<br></font>
<div>
<div></div>
<div class="h5">_______________________________________________<br>CentOS mailing list<br><a href="mailto:CentOS@centos.org">CentOS@centos.org</a><br><a href="http://lists.centos.org/mailman/listinfo/centos" target="_blank">http://lists.centos.org/mailman/listinfo/centos</a><br>
</div></div></blockquote></div><br></div>