Re: [PATCH] fix dom0 builder TAKE 2(was Re: [Xen-ia64-devel] [PATCH] fix dom0 builder)

[Alex Williamson <alex.williamson@xxxxxx>]

On Mon, 2006-10-16 at 12:34 +0900, Isaku Yamahata wrote:
> Looks good and much better than mine.

   Thanks, unfortunately it doesn't behave very well.  A zx1 box has
memory from 0 - 1 GB, and the rest lives above 4GB.  Therefore, if I
boot with dom0_mem=5G, I should have 2GB of memory for dom0 (0-1G,
4-5G).  Here's what the memory map looks like:

(XEN) dom mem: type=13, attr=0x8000000000000008, 
range=[0x0000000000000000-0x0000000000001000) (4KB)
(XEN) dom mem: type=10, attr=0x8000000000000008, 
range=[0x0000000000001000-0x0000000000002000) (4KB)
(XEN) dom mem: type= 6, attr=0x8000000000000008, 
range=[0x0000000000002000-0x0000000000003000) (4KB)
(XEN) dom mem: type= 7, attr=0x0000000000000008, 
range=[0x0000000000003000-0x00000000000a0000) (628KB)
(XEN) dom mem: type=11, attr=0x0000000000000003, 
range=[0x00000000000a0000-0x00000000000c0000) (128KB)
(XEN) dom mem: type= 5, attr=0x8000000000000001, 
range=[0x00000000000c0000-0x0000000000100000) (256KB)
(XEN) dom mem: type= 7, attr=0x0000000000000008, 
range=[0x0000000000100000-0x0000000004000000) (63MB)
(XEN) dom mem: type= 2, attr=0x0000000000000008, 
range=[0x0000000004000000-0x000000000813a000) (65MB)
(XEN) dom mem: type= 7, attr=0x0000000000000008, 
range=[0x000000000813a000-0x000000003f5e4000) (884MB)
(XEN) dom mem: type= 5, attr=0x8000000000000008, 
range=[0x000000003f5e4000-0x000000003fac0000) (4MB)
(XEN) dom mem: type= 7, attr=0x0000000000000008, 
range=[0x000000003fb00000-0x000000003fb08000) (32KB)
(XEN) dom mem: type= 4, attr=0x0000000000000008, 
range=[0x000000003fb08000-0x000000003fb2c000) (144KB)
(XEN) dom mem: type= 9, attr=0x0000000000000008, 
range=[0x000000003fb2c000-0x000000003fb38000) (48KB)
(XEN) dom mem: type= 6, attr=0x8000000000000008, 
range=[0x000000003fb38000-0x0000000040000000) (4MB)
(XEN) dom mem: type=11, attr=0x0000000000000001, 
range=[0x0000000080000000-0x00000000fe000000) (2016MB)
(XEN) dom mem: type=11, attr=0x8000000000000001, 
range=[0x00000000fed00000-0x0000000100000000) (19MB)
(XEN) dom mem: type= 7, attr=0x0000000000000008, 
range=[0x0000000100000000-0x0000000140000000) (1024MB)
(XEN) dom mem: type= 6, attr=0x8000000000000008, 
range=[0x000000027fffe000-0x0000000280000000) (8KB)
(XEN) dom mem: type= 5, attr=0x8000000000000008, 
range=[0x00000040ffd6a000-0x00000040ffda6000) (240KB)
(XEN) dom mem: type= 5, attr=0x8000000000000008, 
range=[0x00000040ffe12000-0x00000040ffe80000) (440KB)
(XEN) dom mem: type= 6, attr=0x8000000000000008, 
range=[0x00000040fffc0000-0x0000004100000000) (256KB)
(XEN) dom mem: type=11, attr=0x0000000000000001, 
range=[0x0000080000000000-0x0000100000000000) (8388608MB)
(XEN) dom mem: type=12, attr=0x8000000000000001, 
range=[0x0003fffffc000000-0x0004000000000000) (64MB)

I see about 2GB of memory in there, we're ok so far.  Dom0 boots up, and
I see:

Memory: 1948096k/2064384k available (10405k code, 115072k reserved, 4256k data, 
288k init)

Everything is still as expected.  Then I login to the console and run
'free':

            total       used       free     shared    buffers     cached
Mem:       5227808    3372608    1855200          0       5408      31552
-/+ buffers/cache:    3335648    1892160
Swap:            0          0          0

This is the first sign that something is really wrong.  When I tried
'xend start', the oom killer took over my system and never gave it back.
Any thoughts?  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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