James,
Before jumping right in to launching the emane demonstrations you should
verify your system is configured to support containers. A simple first
step is to launch a bash shell in a container (as the container's init
process):
# sudo lxc-execute -n foobar /bin/bash
Doing so should yield a 'ps ax' output similar to this:
# ps ax
PID TTY STAT TIME COMMAND
1 pts/9 S 0:00 /usr/lib64/lxc/lxc-init -- /bin/bash
2 pts/9 S 0:00 /bin/bash
14 pts/9 R+ 0:00 ps ax
Additional information about which linux version you are using would be
helpful. More recent versions of Fedora and Ubuntu have become very
similar in terms of container configuration, older versions not so much.
--
Steven Galgano
Adjacent Link LLC
www.adjacentlink.com
On 06/25/2013 10:00 AM, J. Morris wrote:
> I'm trying to set up a fully centralized EMANE installation, and I'm making
> the somewhat reckless assumption that the demonstrations should work if I've
> successfully done so. At the moment, demo one fails to start any nodes, with
> the log noting a failure from lxc-execute:
>
> "lxc_cgroup - write /sys/fs/cgroup/cpu//lxc/node-1/cpu.rt_runtime_us :
> Invalid argument"
>
> Note the double forward slash in the path. In the demo VM, the "node-1"
> directory and its peers are created under /sys/fs/cgroup/cpu -- no lxc
> directory involved. Should I just focus on getting a node to run, and not
> worry about transplanting the demonstrations onto a physical machine, or is
> this a symptom of a problem with the installation?
>
> Thanks,
> James
>
> _______________________________________________
> emane-users mailing list
> [email protected]
> http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
>
_______________________________________________
emane-users mailing list
[email protected]
http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
