1 How to Install Open vSwitch on Linux and FreeBSD
2 ================================================
4 This document describes how to build and install Open vSwitch on a
5 generic Linux or FreeBSD host. For specifics around installation on a
6 specific platform, please see one of these files:
16 To compile the userspace programs in the Open vSwitch distribution,
17 you will need the following software:
21 - The GNU C compiler. We generally test with version 4.1, 4.2, or
24 - pkg-config. We test with version 0.22.
26 - libssl, from OpenSSL, is optional but recommended if you plan to
27 connect the Open vSwitch to an OpenFlow controller. libssl is
28 required to establish confidentiality and authenticity in the
29 connections from an Open vSwitch to an OpenFlow controller. If
30 libssl is installed, then Open vSwitch will automatically build
33 To compile the kernel module on Linux, you must also install the
34 following. If you cannot build or install the kernel module, you may
35 use the userspace-only implementation, at a cost in performance. The
36 userspace implementation may also lack some features. Refer to
37 INSTALL.userspace for more information.
39 - A supported Linux kernel version. Please refer to README for a
40 list of supported versions.
42 The Open vSwitch datapath requires bridging support
43 (CONFIG_BRIDGE) to be built as a kernel module. (This is common
44 in kernels provided by Linux distributions.) The bridge module
45 must not be loaded or in use. If the bridge module is running
46 (check with "lsmod | grep bridge"), you must remove it ("rmmod
47 bridge") before starting the datapath.
49 For optional support of ingress policing, you must enable kernel
50 configuration options NET_CLS_BASIC, NET_SCH_INGRESS, and
51 NET_ACT_POLICE, either built-in or as modules. (NET_CLS_POLICE is
52 obsolete and not needed.)
54 If GRE tunneling is being used it is recommended that the kernel
55 be compiled with IPv6 support (CONFIG_IPV6). This allows for
56 special handling (such as path MTU discovery) of IPv6 packets.
58 To configure HTB or HFSC quality of service with Open vSwitch,
59 you must enable the respective configuration options.
61 To use Open vSwitch support for TAP devices, you must enable
64 - To build a kernel module, you need the same version of GCC that
65 was used to build that kernel.
67 - A kernel build directory corresponding to the Linux kernel image
68 the module is to run on. Under Debian and Ubuntu, for example,
69 each linux-image package containing a kernel binary has a
70 corresponding linux-headers package with the required build
73 If you are working from a Git tree or snapshot (instead of from a
74 distribution tarball), or if you modify the Open vSwitch build system
75 or the database schema, you will also need the following software:
77 - Autoconf version 2.64 or later.
79 - Automake version 1.10 or later.
81 - Python 2.x, for x >= 4.
83 If you modify the ovsdbmonitor tool, then you will also need the
86 - pyuic4 from PyQt4 (http://www.riverbankcomputing.co.uk).
88 To run the unit tests, you also need:
90 - Perl. Version 5.10.1 is known to work. Earlier versions should
93 If you modify the vswitchd database schema, then the E-R diagram in
94 the ovs-vswitchd.conf.db(5) manpage will be updated properly only if
95 you have the following:
97 - "dot" from graphviz (http://www.graphviz.org/).
99 - Perl. Version 5.10.1 is known to work. Earlier versions should
102 - Python 2.x, for x >= 4.
104 If you are going to extensively modify Open vSwitch, please consider
105 installing the following to obtain better warnings:
107 - "sparse" version 0.4.4 or later
108 (http://www.kernel.org/pub/software/devel/sparse/dist/).
112 Installation Requirements
113 -------------------------
115 The machine on which Open vSwitch is to be installed must have the
118 - libc compatible with the libc used for build.
120 - libssl compatible with the libssl used for build, if OpenSSL was
123 - On Linux, the same kernel version configured as part of the build.
125 - For optional support of ingress policing on Linux, the "tc" program
126 from iproute2 (part of all major distributions and available at
127 http://www.linux-foundation.org/en/Net:Iproute2).
129 On Linux you should ensure that /dev/urandom exists. To support TAP
130 devices, you must also ensure that /dev/net/tun exists.
132 To run the ovsdbmonitor tool, the machine must also have the following
135 - Python 2.x, for x >= 4.
137 - Python Twisted Conch.
143 - Python Zope interface module.
145 (On Debian "lenny" the above can be installed with "apt-get install
146 python-json python-qt4 python-zopeinterface python-twisted-conch".)
148 Building and Installing Open vSwitch for Linux or FreeBSD
149 =========================================================
151 Once you have installed all the prerequisites listed above in the Base
152 Prerequisites section, follow the procedure below to build.
154 1. If you pulled the sources directly from an Open vSwitch Git tree,
155 run boot.sh in the top source directory:
159 2. In the top source directory, configure the package by running the
160 configure script. You can usually invoke configure without any
165 By default all files are installed under /usr/local. If you want
166 to install into, e.g., /usr and /var instead of /usr/local and
167 /usr/local/var, add options as shown here:
169 % ./configure --prefix=/usr --localstatedir=/var
171 To use a specific C compiler for compiling Open vSwitch user
172 programs, also specify it on the configure command line, like so:
174 % ./configure CC=gcc-4.2
176 To build the Linux kernel module, so that you can run the
177 kernel-based switch, pass the location of the kernel build
178 directory on --with-linux. For example, to build for a running
181 % ./configure --with-linux=/lib/modules/`uname -r`/build
183 If you wish to build the kernel module for an architecture other
184 than the architecture of the machine used for the build, you may
185 specify the kernel architecture string using the KARCH variable
186 when invoking the configure script. For example, to build for MIPS
189 % ./configure --with-linux=/path/to/linux KARCH=mips
191 The configure script accepts a number of other options and honors
192 additional environment variables. For a full list, invoke
193 configure with the --help option.
195 3. Run GNU make in the top source directory, e.g.:
199 or if GNU make is installed as "gmake":
203 For improved warnings if you installed "sparse" (see
204 "Prerequisites"), add C=1 to the command line.
206 4. Consider running the testsuite. Refer to "Running the Testsuite"
207 below, for instructions.
209 5. Become root by running "su" or another program.
211 6. Run "make install" to install the executables and manpages into the
212 running system, by default under /usr/local.
214 7. If you built kernel modules, you may load them with "insmod", e.g.:
216 % insmod datapath/linux/openvswitch.ko
218 You may need to specify a full path to insmod, e.g. /sbin/insmod.
219 To verify that the modules have been loaded, run "/sbin/lsmod" and
220 check that openvswitch is listed.
222 If the "insmod" operation fails, look at the last few kernel log
223 messages (e.g. with "dmesg | tail"):
225 - The message "openvswitch: exports duplicate symbol
226 br_should_route_hook (owned by bridge)" means that the bridge
227 module is loaded. Run "/sbin/rmmod bridge" to remove it.
229 If "/sbin/rmmod bridge" fails with "ERROR: Module bridge does
230 not exist in /proc/modules", then the bridge is compiled into
231 the kernel, rather than as a module. Open vSwitch does not
232 support this configuration (see "Build Requirements", above).
234 - The message "openvswitch: exports duplicate symbol
235 dp_ioctl_hook (owned by ofdatapath)" means that the ofdatapath
236 module from the OpenFlow reference implementation is loaded.
237 Run "/sbin/rmmod ofdatapath" to remove it. (You might have to
238 delete any existing datapaths beforehand, using the "dpctl"
239 program included with the OpenFlow reference implementation.
240 "ovs-dpctl" will not work.)
242 - Otherwise, the most likely problem is that Open vSwitch was
243 built for a kernel different from the one into which you are
244 trying to load it. Run "modinfo" on openvswitch.ko and on
245 a module built for the running kernel, e.g.:
247 % /sbin/modinfo openvswitch.ko
248 % /sbin/modinfo /lib/modules/`uname -r`/kernel/net/bridge/bridge.ko
250 Compare the "vermagic" lines output by the two commands. If
251 they differ, then Open vSwitch was built for the wrong kernel.
253 - If you decide to report a bug or ask a question related to
254 module loading, please include the output from the "dmesg" and
255 "modinfo" commands mentioned above.
257 There is an optional module parameter to openvswitch.ko called
258 vlan_tso that enables TCP segmentation offload over VLANs on NICs
259 that support it. Many drivers do not expose support for TSO on VLANs
260 in a way that Open vSwitch can use but there is no way to detect
261 whether this is the case. If you know that your particular driver can
262 handle it (for example by testing sending large TCP packets over VLANs)
263 then passing in a value of 1 may improve performance. Modules built for
264 Linux kernels 2.6.37 and later, as well as specially patched versions
265 of earlier kernels, do not need this and do not have this parameter. If
266 you do not understand what this means or do not know if your driver
267 will work, do not set this.
269 Once you verify that the kernel modules load properly, you should
272 % make modules_install
274 8. Initialize the configuration database using ovsdb-tool, e.g.:
276 % mkdir -p /usr/local/etc/openvswitch
277 % ovsdb-tool create /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema
282 Before starting ovs-vswitchd itself, you need to start its
283 configuration database, ovsdb-server. Each machine on which Open
284 vSwitch is installed should run its own copy of ovsdb-server.
285 Configure it to use the database you created during step 7 of
286 installation, above, to listen on a Unix domain socket, to connect to
287 any managers specified in the database itself, and to use the SSL
288 configuration in the database:
290 % ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock \
291 --remote=db:Open_vSwitch,manager_options \
292 --private-key=db:SSL,private_key \
293 --certificate=db:SSL,certificate \
294 --bootstrap-ca-cert=db:SSL,ca_cert \
297 (If you built Open vSwitch without SSL support, then omit
298 --private-key, --certificate, and --bootstrap-ca-cert.)
300 Then initialize the database using ovs-vsctl. This is only
301 necessary the first time after you create the database with
302 ovsdb-tool (but running it at any time is harmless):
304 % ovs-vsctl --no-wait init
306 Then start the main Open vSwitch daemon, telling it to connect to the
307 same Unix domain socket:
309 % ovs-vswitchd --pidfile --detach
311 Now you may use ovs-vsctl to set up bridges and other Open vSwitch
312 features. For example, to create a bridge named br0 and add ports
313 eth0 and vif1.0 to it:
315 % ovs-vsctl add-br br0
316 % ovs-vsctl add-port br0 eth0
317 % ovs-vsctl add-port br0 vif1.0
319 Please refer to ovs-vsctl(8) for more details.
324 When you upgrade Open vSwitch from one version to another, you should
325 also upgrade the database schema:
327 1. Stop the Open vSwitch daemons, e.g.:
329 % kill `cd /usr/local/var/run/openvswitch && cat ovsdb-server.pid ovs-vswitchd.pid`
331 2. Install the new Open vSwitch release.
333 3. Upgrade the database, in one of the following two ways:
335 - If there is no important data in your database, then you may
336 delete the database file and recreate it with ovsdb-tool,
337 following the instructions under "Building and Installing Open
338 vSwitch for Linux or FreeBSD".
340 - If you want to preserve the contents of your database, back it
341 up first, then use "ovsdb-tool convert" to upgrade it, e.g.:
343 % ovsdb-tool convert /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema
345 4. Start the Open vSwitch daemons as described under "Building and
346 Installing Open vSwitch for Linux or FreeBSD" above.
348 Running the Testsuite
349 =====================
351 Open vSwitch includes a testsuite. Before you submit patches
352 upstream, we advise that you run the tests and ensure that they pass.
353 If you add new features to Open vSwitch, then adding tests for those
354 features will ensure your features don't break as developers modify
355 other areas of Open vSwitch.
357 You must configure and build Open vSwitch (steps 1 through 3 in
358 "Building and Installing Open vSwitch for Linux or FreeBSD" above)
359 before you run the testsuite. You do not need to install Open vSwitch
360 or to build or load the kernel module to run the testsuite. You do
361 not need supervisor privilege to run the testsuite.
363 To run all the unit tests in Open vSwitch, one at a time:
365 This takes under 5 minutes on a modern desktop system.
367 To run all the unit tests in Open vSwitch, up to 8 in parallel:
368 make check TESTSUITEFLAGS=-j8
369 This takes under a minute on a modern 4-core desktop system.
371 To see a list of all the available tests, run:
372 make check TESTSUITEFLAGS=--list
374 To run only a subset of tests, e.g. test 123 and tests 477 through 484:
375 make check TESTSUITEFLAGS='123 477-484'
376 (Tests do not have inter-dependencies, so you may run any subset.)
378 To run tests matching a keyword, e.g. "ovsdb":
379 make check TESTSUITEFLAGS='-k ovsdb'
381 To see a complete list of test options:
382 make check TESTSUITEFLAGS=--help
384 The results of a testing run are reported in tests/testsuite.log.
385 Please report test failures as bugs and include the testsuite.log in
388 If you have "valgrind" installed, then you can also run the testsuite
389 under valgrind by using "make check-valgrind" in place of "make
390 check". All the same options are available via TESTSUITEFLAGS. When
391 you do this, the "valgrind" results for test <N> are reported in files
392 named tests/testsuite.dir/<N>/valgrind.*. You may find that the
393 valgrind results are easier to interpret if you put "-q" in
394 ~/.valgrindrc, since that reduces the amount of
396 Sometimes a few tests may fail on some runs but not others. This is
397 usually a bug in the testsuite, not a bug in Open vSwitch itself. If
398 you find that a test fails intermittently, please report it, since the
399 developers may not have noticed.
404 Please report problems to bugs@openvswitch.org.