Re: Cannot start xend: ERROR Internal error: Could not lock memory for Xen hypercall (35 = Resource temporarily unavailabl)

[Stephane Bortzmeyer <stephane%sources.org@localhost>]

On Sun, May 31, 2009 at 10:43:12PM +0200,
 Jean-Yves Migeon <jeanyves.migeon%free.fr@localhost> wrote 
 a message of 19 lines which said:

> ulimit -a before calling xend, and paste the result here.

% ulimit -a        
-t: cpu time (seconds)         unlimited
-f: file size (blocks)         unlimited
-d: data seg size (kbytes)     262144
-s: stack size (kbytes)        2048
-c: core file size (blocks)    unlimited
-m: resident set size (kbytes) 52316
-l: locked-in-memory size (kb) 52316
-u: processes                  160
-n: file descriptors           128
-N  9: socket buffer size (kb) unlimited
-v: virtual memory size (kb)   unlimited

(This is after I tried a 'ulimit -l unlimited', which increased the
locked-in-memory size but changed nothing for xend.)