Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Mininet 2.1.0 Release Notes
This document contains supplementary information and issues not included in that file.
Documentation for Examples and Tests
The examples have Python docstring documentation, and can be used as modules, e.g.
sudo python -m mininet.examples.nat
Their components may also be imported, but they should be considered volatile and not part of the official Mininet API. Their documentation is also not currently included at api.mininet.org or generated with
make doc. However, you may wish to look at the code and
README.md file in the examples/ directory.
The tests are not included in the Mininet
.egg, nor are they documented at api.mininet.org, but they are included in the Mininet source tree.
Potential VirtualBox Issues
If VirtualBox (or any other virtual machine monitor) cannot import the
.ovfdirectly, try creating a new VM using the
.vmdkfile as its disk.
VirtualBox may complain about missing hardware on initial import - you may safely ignore this message.
We've added a symlink to the top-level examples directory from the mininet code directory to make examples importable. If you are using VirtualBox and clone the repository to a shared folder, the symlink will be broken. This is because VirtualBox does not allow guests to create symlinks in shared folders by default for security reasons. To enable symlink creation, you should do the following:
- Shut down your VM and quit the VirtualBox Manager
- Run the following command on your host OS:
VBoxManage setextradata VM_NAME
- Restart your VM
Currently one of the bandwidth limit tests in
test_hifi.pyfails (or sometimes fails) due to low bandwidth in OVS in user mode on Ubuntu 13.10/Saucy Salamander development builds (mid-September); if you run into this problem, the workaround is either to use kernel-mode OVS or an earlier Ubuntu release.
Some performance tests (e.g.
test_linearbandwidth.py) can occasionally fail in virtualized or non-quiescent environments due to performance variance, scheduling, or timing skew. Others may fail if they hit resource limits of the underlying system (e.g. a netbook or a VM with limited resources.)
testSimplePerfwill usually succeed, but will occasionally fail if you get lucky (0% loss) or unlucky (100% loss).
--switch usercannot be used with
--mac; there appears to be a bug where the reference switch (and presumably its derivates like the CPqD switch) does not correctly match and forward packets when the MAC address is
--switch ivscannot be used with more than a few switches; a bug has been submitted to the IVS developers.
--host rtmay not work correctly on multiprocessors (use
--host cfsinstead, or run on a single processor.)
xtermCLI command does not work in the
There is currently an annoying bug with certain kernels which may result in messages similar to the following:
[ 176.965603] unregister_netdevice: waiting for h1-eth0 to become free. Usage count = 1 [ 185.508516] unregister_netdevice: waiting for lo to become free. Usage count = 2 [ 187.245149] unregister_netdevice: waiting for h1-eth0 to become free. Usage count = 1 [ 195.781125] unregister_netdevice: waiting for lo to become free. Usage count = 2 [ 197.521721] unregister_netdevice: waiting for h1-eth0 to become free. Usage count = 1 [ 206.053467] unregister_netdevice: waiting for lo to become free. Usage count = 2
This bug has been reported on launchpad.net, and there is unfortunately no solution yet other than rebooting the VM and/or trying a different kernel.
Here are the data points we have so far:
Kernel Ubuntu Version Bug Frequency
12.04 (not .3) Never
After 2.1.0 was released, the URL for the
oflops repository changed, breaking the default
install.sh -a installation. 2.1.0p1 fixes this problem and also includes a few additional minor changes.