On Wed, Mar 22, 2006 at 04:30:39PM +0100, Blaisorblade wrote:
> I remember this, I didn't have many other things to suggest (apart TT mode)
> and that setting is needed anyway (actually it's needed when you go _over_
> 256M per guest).
To be precise, it's necessary when you have UML processes wi
On Wednesday 22 March 2006 12:04, Stefano Melchior wrote:
> On Tue, Mar 21, 2006 at 07:54:08PM +0100, Blaisorblade wrote:
> Dear all,
>
> > No, that crash is likely a race condition and the code treats
> > mem=256{m,M} the same way.
> > Verified in arch/um/kernel/physmem.c:uml_mem_setup and
> > lib
On Wed, Mar 22, 2006 at 12:04:00PM +0100, Stefano Melchior wrote:
> thus the point is if you need to disable TT mode by default, isn't it?
> Now user-mode-linux is in debian "unstable" [1] and I need to provide a
> config file as default configuration for the pkg: you suggested me to act
> this way
On Tuesday 21 March 2006 21:51, Jeff Dike wrote:
> On Tue, Mar 21, 2006 at 07:54:08PM +0100, Blaisorblade wrote:
> > However, test increasing /proc/sys/vm/max_map_count
>
> This only bites you when you have large UML processes - I don't think it
> can cause a crash on boot.
I remember this, I didn
On Tue, Mar 21, 2006 at 07:54:08PM +0100, Blaisorblade wrote:
Dear all,
>
> No, that crash is likely a race condition and the code treats mem=256{m,M}
> the
> same way.
> Verified in arch/um/kernel/physmem.c:uml_mem_setup and lib/cmdline.c:memparse.
>
> However, test increasing /proc/sys/vm/ma
On Tue, Mar 21, 2006 at 07:54:08PM +0100, Blaisorblade wrote:
> However, test increasing /proc/sys/vm/max_map_count
This only bites you when you have large UML processes - I don't think it
can cause a crash on boot.
Jeff
-
On Tuesday 21 March 2006 15:50, Stefano Melchior wrote:
> On Tue, Mar 21, 2006 at 03:26:25PM +0100, Stefano Melchior wrote:
> Dear all,
> [...]
> I also noticed that, from manual page, if you use:
> mem=memory
> This controls how much "physical" memory the kernel
> allocates for the system. The si
On Tue, Mar 21, 2006 at 03:26:25PM +0100, Stefano Melchior wrote:
> - while I added the mem=256M option at the command line, I obtained the
> following error:
> Any suggestion?
Do you have CONFIG_MODE_TT enabled? I think disabling it is the fix for this.
Jeff
On Tue, Mar 21, 2006 at 03:26:25PM +0100, Stefano Melchior wrote:
Dear all,
[...]
I also noticed that, from manual page, if you use:
mem=memory
This controls how much "physical" memory the kernel
allocates for the system. The size is specified as a number
followed by one of ’k’, ’K’, ’m’, ’M’,
