The fact you get the "limiting..." message in the -B case implies the value was accepted and acted upon.
I suspect that this cannot be set in /etc/system on x86. Walking through the x86 startup code shows that it may be read too late in the boot cycle to make a difference. In startup(), we call startup_memlist() first (which implements the check for npages and physmem and calls kphysm_init() to initialise the now limited amount of memory), then call startup_kmem() which triggers the read of /etc/system.
Hope that helps, Brian Roy Sigurd Karlsbakk wrote:
Hi all It seems the physmem option in /etc/system and as given to the kernel boot is broken. Booting a system with physmem set to something lower than its actual size fails to give any message, and the system has its full amount of memory available. Same applies to using kernel options (-B physmem=xxx). The latter shows a warning in the kernel log that memory has been limited, but tools like 'top' show the full amount of memory. I fist saw this on OI148, but later checked if the issue was reproducable in S11ex, which it was. Vennlige hilsener / Best regards roy
-- Brian Ruthven Solaris Network RPE (Sustaining) Oracle UK _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
