carlopmart wrote:
> Sadique Puthen wrote:
>> carlopmart wrote:
>>> Hi all,
>>>
>>>  I have an extrange problem on a rhel5.1 xen host. I have 4 xen
>>> guests running: two para-virtualized and two HVM. Memory asignements
>>> are:
>>>
>>> xentop - 09:34:05   Xen 3.1.0-53.el5
>>> 5 domains: 1 running, 4 blocked, 0 paused, 0 crashed, 0 dying, 0
>>> shutdown
>>> Mem: 3145268k total, 2680980k used, 464288k free    CPUs: 2 @ 3213MHz
>>>
>>> NAME       STATE    CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k)
>>> Domain-0   -----r         71    0.0     262192    8.3   no limit
>>> RhelClu01  --b---         44    0.0     655184   20.8     655360
>>> RhelClu02  --b---         24    0.0     655224   20.8     655360
>>> RhelFWInt  --b---         45    0.0     532352   16.9     540672
>>> RhelFWPub  --b---         39    0.0     401280   12.8     409600
>>>
>>> My xen host has 3GB of RAM. I need to start up a fifth guest with
>>> 512M of RAM assigned, but I can't because free memory for guests are
>>> 464288. But why??
>>>
>>> Doing a simple arithmetic operation:
>>> (262192+655184+655224+532352+401280)-3145268= -639036 free memory,
>>> but xentop says that only 464288kb of RAM are free. Where are
>>> 174748kb of RAM that xentop doesn't shows me? Maybe the problem could
>>> be this grub params: kernel /xen.gz-2.6.18-53.el5 dom0_mem=256M
>>> lowmem_emergency_pool=16M [EMAIL PROTECTED]
>>
>> This reserves 128MB of mem for crash kernel and you would only be able
>> to see less 128MB from your actual memory on the dom0.
>>
> 
> Thanks Sadique. Can I remove crashkernel param and leave
> lowmem_emergency_pool without break something???

Removing the crashkernel parameter will disable kdump from being able to
capture a vmcore in the event of a system crash, but yes, you can remove
it without breaking anything else. So that explains where 128M of your
memory went, and I can probably explain the rest: the xen hypervisor
reserves some memory for itself that it doesn't expose even to the dom0
kernel.

-- 
Jarod Wilson
[EMAIL PROTECTED]


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to