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’,
Dear all,
I may be wrong but I encountered a strange problem:
- I downloaded a root_fs from http://uml.nagafix.co.uk/ (debian)
- I user my own user-mode-linux pkg for debian (upcoming on debian
unstable);
- I launched the following command:
ste$ linux ubd0=Debian-3.1-x86-root_fs con0=fd:0 con=p
