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

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Thu, Dec 31, 2009 at 04:35:07PM -0500, James Pifer wrote:
> On Thu, 2009-12-31 at 21:48 +0200, Pasi Kärkkäinen wrote:
> > On Thu, Dec 31, 2009 at 03:45:36PM -0500, James Pifer wrote:
> > > > So what does "xm info" say about free memory? How much does the guest
> > > > you're trying to start have memory configured for it? 
> > > > 
> > > > -- Pasi
> > > 
> > > The domU only has 512meg. 
> > >
> > 
> > Ok. Really weird. 
> > How about dom0, does it have free memory? 
> > 
> > This was SLES11? 
> > 
> > -- Pasi
> > 
> > 
> > > # xm info
> > > host                   : xen06
> > > release                : 2.6.27.19-5-xen
> > > version                : #1 SMP 2009-02-28 04:40:21 +0100
> > > machine                : x86_64
> > > nr_cpus                : 16
> > > nr_nodes               : 1
> > > cores_per_socket       : 4
> > > threads_per_core       : 2
> > > cpu_mhz                : 2533
> > > hw_caps                : 
> > > bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
> > > virt_caps              : hvm
> > > total_memory           : 32757
> > > free_memory            : 12769
> > > max_free_memory        : 13280
> > > max_para_memory        : 13276
> > > max_hvm_memory         : 13236
> > > node_to_cpu            : node0:0-15
> > > node_to_memory         : node0:12769
> > > xen_major              : 3
> > > xen_minor              : 4
> > > xen_extra              : .1_19718_04-26.
> > > 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 
> > > xen_scheduler          : credit
> > > xen_pagesize           : 4096
> > > platform_params        : virt_start=0xffff800000000000
> > > xen_changeset          : 19718
> > > cc_compiler            : gcc version 4.3.2 [gcc-4_3-branch revision 
> > > 141291] (SUSE Linux)
> > > cc_compile_by          : abuild
> > > cc_compile_domain      : 
> > > cc_compile_date        : Wed Oct 14 00:02:21 UTC 2009
> > > xend_config_format     : 4
> > > 
> > > 
> > > Thanks,
> > > James
> > > 
> 
> Looks like dom0 is just about out of memory. It currently has 1 gb of
> RAM. Looks like I changed menu.lst on Dec 12 to give it 2 gb of RAM, but
> I haven't had a chance to restart it. It's been up for 29 days. It's a
> dual quad core machine with 32gb of ram. It will probably run 12-18
> domU's when all is said and done ranging anywhere from 512M to 4gb of
> ram. Mixed Windows and Linux. Do you think 2gb of ram is enough for dom0
> or should I go more, like 3 or 4gb?
> 

2GB definitely should be enough.. afaik.

> "top" gives me:
> top - 14:18:13 up 29 days, 17:41,  3 users,  load average: 0.47, 0.77, 0.71
> Tasks: 302 total,   3 running, 299 sleeping,   0 stopped,   0 zombie
> Cpu(s):  0.4%us,  0.1%sy,  0.0%ni, 98.4%id,  0.7%wa,  0.0%hi,  0.0%si,  0.4%st
> Mem:   1047040k total,  1036656k used,    10384k free,     7816k buffers
> Swap:  2104472k total,  2104156k used,      316k free,    53876k cached
> 

So what's eating all the memory and swap? 

-- Pasi


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