I have compiled EMANE and run the first two demonstrations on OpenSUSE
12.3 (x86_64).

uname -a
Linux jib 3.7.10-1.16-desktop #1 SMP PREEMPT Fri May 31 20:21:23 UTC 2013 
(97c14ba) x86_64 x86_64 x86_64 GNU/Linux

        Some of the problems that were encountered are:

1)      scripts/lxc-demo-stop.sh is missing a getopts parameter.

2)      scripts/lxc-demo-start.sh, and the scripts it calls, uses
        lxc-execute to set up the containers.  It then uses lxc-ls
        to check if the containers have been set up.

        In the versions of lxc I've tried (0.8.0 and 0.9.0),
        the bookeeping enteries used by lxc-ls are set by
        lxc-create.  They are not set when lxc-execute is used
        to build the containers.  Thus, lxc-ls fails.

3)      I ran emane su'd to root.  The initial PATH didn't include
        the right directories and/or I created confusion by installing
        under "/usr/local".  The upshot was that I had to explicitly
        point to the locations of some of the executables used
        in the scripts, and/or change certain configuration parameters.

        For example, the file "scripts/funcitons" has a reference to
        "route" hard-coded into it.  I had to change that to "/sbin/route",
        otherwise the pipe containing "route" fails.

        In another file, I changed "olsrd" to "/usr/local/sbin/olsrd".

4)      In order to run with the realtime option, I had to set a value into:

/sys/fs/cgroup/cpu,cpuacct/lxc/cpu.rt_runtime_us

        which is greater than (or equal to?) the sum of the values that the
        demonstration scripts place in:

/sys/fs/cgroup/cpu,cpuacct/lxc/node-*/cpu.rt_runtime_us

        Perhaps earlier Linux kernels didn't enforce this constraint?


        Upon request, I can provide further details on the hair-pulling and
workarounds I employed.

                                        Craig Milo Rogers
_______________________________________________
emane-users mailing list
[email protected]
http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users

Reply via email to