WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Memory problems persist... Cannot allocate memory

On Fri, Jan 22, 2010 at 10:06:47PM -0500, James Pifer wrote:
> > Just for reference, back in the Xen 2.0 days I used to have 192 MB of
> > RAM for dom0.. and that was enough.
> > 
> > Nowadays I usually give dom0 512 MB of RAM, or in bigger machines 1024 MB.
> > That is usually enough for a Xen-only server machine (without any local 
> > desktop/X use).
> > 
> > So.. you need to make sure there's nothing leaking memory in dom0. 
> > Xen management tools will obviously require some available memory in dom0 
> > to work correctly.
> > 
> > -- Pasi
> > 
> 
> Here we go again.... I wanted to start another domU on one of me xen
> servers tonight and I'm getting not able to allocate memory again. Check
> out the following stats. 
> 
> If anyone sees anything I'd love to hear it... Please let me know if
> there's anything else I should post.
> 
> Thanks,
> James
> 
> 
> # top
> 
> top - 20:02:11 up 39 days,  9:03,  2 users,  load average: 0.11, 0.85, 1.25
> Tasks: 256 total,   1 running, 255 sleeping,   0 stopped,   0 zombie
> Cpu(s):  0.0%us,  0.1%sy,  0.0%ni, 98.5%id,  0.5%wa,  0.0%hi,  0.1%si,  0.8%st
> Mem:   2095616k total,  1689848k used,   405768k free,    11624k buffers
> Swap:  2104472k total,  1476856k used,   627616k free,   406620k cached
>

xend is using 1,8 GB of memory? Is that normal? Even RES is almost 1 GB..

Please post the following logs:

- "xm log" 
- "xm dmesg"
- dom0 "dmesg"
- and if there's something related in /var/log/messages or /var/log/syslog

-- Pasi


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

<Prev in Thread] Current Thread [Next in Thread>