Gus Wirth wrote: > Joshua Penix wrote: >> On Dec 19, 2007, at 2:11 PM, Gregory K. Ruiz-Ade wrote: >> >>> Would it be possible to allocate some more memory to the VM without >>> breaking anything? I realize it would require a bounce of the image. >> No. I already tried this. :) No matter how much I assign it in Xen, it >> refuses to see more than ~900MB. I have no clue why. >> > > The kernel probably doesn't have HIMEM enabled. I have 1GB RAM in my > system. From my own running kernel, extracted from dmesg: > > [snip] > BIOS-provided physical RAM map: > BIOS-e820: 0000000000000000 - 000000000009f800 (usable) > BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) > BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) > BIOS-e820: 0000000000100000 - 000000003fff0000 (usable) > BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS) > BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data) > BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) > BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) > BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) > 127MB HIGHMEM available. > 896MB LOWMEM available. > found SMP MP-table at 000f5520 > > [snip] > > It looks like you are restricted to the LOWMEM limit. >
That 896 MB limit would seem to explain the allocation behavior. I forget now, are we running a 32bit kernel? If so, a side question might be: was that an expediency choice? is a 64bit upgrade in the winds, whenever the issue goes away -- perhaps hw-compatiblity or? Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer
