Le samedi 23 janvier 2010 à 21:17 -0500, James Pifer a écrit :
> On Sat, 2010-01-23 at 23:02 +0100, jpp@xxxxxxxxxxxxxxxxxx wrote:
> > Hello,
> >
> > What is the output of "xm top" and the memory size for the crashing
> > domU ?
> >
> > Regards
> >
> > JP Pozzi
> >
>
> xentop - 19:14:32 Xen 3.4.1_19718_04-26.
> 9 domains: 1 running, 8 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
> Mem: 33543988k total, 17741584k used, 15802404k free CPUs: 16 @ 2533MHz
> NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%)
> VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID
> Domain-0 -----r 1246289 109.5 2095616 6.2 no limit n/a
> 16 0 0 0 0 0 0 0 0
> servercwi0 --b--- 75887 1.5 1052588 3.1 1052672 3.1
> 2 1 0 0 2 0 0 0 0
> serverhpd0 --b--- 221480 0.0 4194304 12.5 4194304 12.5
> 4 1 180634125 732323572 1 0 42849 778081 0
> servernoc0 --b--- 4407 0.0 3145728 9.4 3145728 9.4
> 4 1 33771 1808661 1 7 29602 912013 0
> serverpam2 --b--- 237517 2.8 1052588 3.1 1052672 3.1
> 2 1 0 0 1 0 0 0 0
> serverrly0 --b--- 169632 0.5 4194304 12.5 4194304 12.5
> 4 1 122085682 105533360 1 0 306821 1716024 0
> servervre0 --b--- 32635 1.3 528300 1.6 528384 1.6
> 1 1 535378 13214394 2 28 190040 1548933 0
> servervre0 --b--- 39299 1.0 528300 1.6 528384 1.6
> 1 1 890550 12268039 2 290 1143690 3083914 0
> servervre0 --b--- 17685 1.4 528300 1.6 528384 1.6
> 1 1 1182612 4006256 2 0 1520182 5525180 0
>
>
> By crashing I assume you mean the cannot allocate memory? Only 1024meg.
>
> Thanks,
> James
>
Hello,
I see that your Dom0 has 33543988k #32GB, is it all the memory in the
server?
If so it is possible that after some "ballooning" and memory allocation
the memory is too unorganized that the allocator can't find suitable
chunks of memory. I had had that problem after a system upgrade where
the "menu.lst" (or grub.fcg) was recreated without the tuning
parameters.
I think that 32GB is fa too much for the Dom0, usually Dom0 is limited
to a value between 1024M and 3072M with the dom0_mem=xxxx in the
grub.cfg, the memory of Dom0 is mainly used for buffer cache on behalf
of the Domus.
It is also often useful to use the parameter "dom0_min_mem=xxx" in the
xend.config file. In my systems I use the same value eg :
(dom0-min-mem 2048)
(enable-dom0-ballooning no)
in xend-config.sxo
and
multiboot /xen-3.4.gz /xen-3.4.gz noreboot dom0_mem=2048M
in grub.cfg.
I have had problems with "ballonning yes" if domUs are stopped and
started many times without a server reboot (memory fargmentation ?).
Regards
JP Pozzi
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home