Dans l'épisode précédent (Mon, Sep 26 2005 - 11:59), Lubomir Sedlacik nous apprenait que :
> On Mon, Sep 26, 2005 at 11:19:54AM +0200, Joel CARNAT wrote:
> > I'm trying to get qemu use more than 64Mbits of RAM (with 3.0_BETA and
> > 3.99.8, both i386, and 512Mo of RAM). Google points me to ulimit but
> > it doesn't seem to be my problem (my bash has ulimit=unlimited, and
> > running qemu as root isn't better).
> > 
> > I noticed some value in sysctl :
> > proc.curproc.rlimit.datasize.soft = 134217728
> > proc.curproc.rlimit.datasize.hard = 1073741824
> > 
> > proc.curproc.rlimit.datasize.soft looks like the one than has to be
> > modified. I tried doing so :
> > # sudo sysctl -w proc.curproc.rlimit.datasize.soft=0
> > proc.curproc.rlimit.datasize.soft: 134217728 -> 0
> > # sudo sysctl -w proc.curproc.rlimit.datasize.soft=536870912
> > proc.curproc.rlimit.datasize.soft: 134217728 -> 536870912
> 
> you are raising limits for the sysctl(8) process itself.
> 
> > each time, it goes back to it's initial value...
> > so :
> > 1. any trick to have qemu use 128Mo or 256Mo ?
> 
> you need to raise the limits for the shell executing qemu.  use
> ulimit/limit commands of your shell to change datasize soft limit (e.g.,
> for bourne style shells: ulimit -d).
> 

ah... it works better when I do 'ulimit -d 393216'.
I thought `ulimit` saying "unlimited" meant there were no restriction.

thanks a lot !

-- 
,-- This mail runs ---------.
`------------ NetBSD/i386 --'