On Wednesday 17 January 2007 18:15, Pravin wrote:
> Thanx :-)
> Its working now.... :-)
> One more thing that I would like to tell here.
> I did used same compiled kernel on other machine which was having
> And that kernel 2.6.19 without your patch did worked fine....
> but same kernel 2.6.19 was not working on my machine which is Debian
> 2.6.18. After applying your patch and changing the configuration to
> HOST_2G_2G its working fine now on my Debian machine 2.6.18.
> Can I know what excatly was the problem... ?
Usually the host kernel "gives"* a certain space (3G) to userspace apps. Some
host kernels give less memory (say 2,75G, 2G, or even 1G) to userspace apps
(these days, it depends on the CONFIG_VMSPLIT_* settings, before it could be
tuned via external patches like -ck patchset or probably others).
Most application use the available memory, but UML, for now, needs to know
that it can use a given amount - say 2G. It will run fine when more memory is
available, but not when less memory is available.
At last, why different splits? While 3G is usual (normally named 3G/1G), on a
host with 1G of RAM you either use HIGHMEM (with a little slowdown) or use a
* This is "virtual address space", not a statical split assigning physical RAM
to different purposes - but I won't go in the details here.
> My main objective is to run SELinux on UML kernel and test it.
Probably Antoine Martin is the one having more experience on UML+SELinux. This
is his page on the argument:
> Let me know if there is anything I can do to help here.
> On 1/17/07, Blaisorblade <blaisorblade@...> wrote:
> > You mentioned trying to use CONFIG_HOST_VMSPLIT to solve a problem, that
> > is of little use without this applied, if you run UML in SKAS0 mode.
> > ---------- Forwarded Message ----------
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
Chiacchiera con i tuoi amici in tempo reale!