X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=INSTALL.Linux;h=177a9cd13b7d2eb4df426a2f41be5e13949543d7;hb=79c9f2ee7883b52860c76c3730725f5731402874;hp=c0344f23010bdad00857e7010f6e9e8f70f3be56;hpb=a4af00400a835eb87569ba40e21874c05e872c0f;p=openvswitch diff --git a/INSTALL.Linux b/INSTALL.Linux index c0344f23..177a9cd1 100644 --- a/INSTALL.Linux +++ b/INSTALL.Linux @@ -61,7 +61,7 @@ If you are working from a Git tree or snapshot (instead of from a distribution tarball), or if you modify the Open vSwitch build system, you will also need the following software: - - Autoconf version 2.63 or later. + - Autoconf version 2.64 or later. - Automake version 1.10 or later. @@ -155,23 +155,40 @@ Prerequisites section, follow the procedure below to build. To verify that the modules have been loaded, run "/sbin/lsmod" and check that openvswitch_mod is listed. -Configuration -============= +7. Initialize the configuration database using ovsdb-tool, e.g.: -Open vSwitch is configured primarily through a configuration file, -whose name is specified on the ovs-vswitchd command line. Please -refer to ovs-vswitchd(8) and ovs-vswitchd.conf(5) for information on -how to start ovs-vswitchd and the syntax of its configuration file, -respectively. + % ovsdb-tool create /usr/local/etc/ovs-vswitchd.conf.db vswitchd/vswitch.ovsschema -At runtime, you may make ovs-vswitchd reload its configuration file -and update its configuration accordingly by sending it a SIGHUP -signal. The ovs-appctl utility can also be used to do this: +Startup +======= - % ovs-appctl vswitchd/reload +Before starting ovs-vswitchd itself, you need to start its +configuration database, ovsdb-server. Configure it to use the +database you created during step 7 of installation, above, and to +listen on a Unix domain socket, e.g.: -In the latter case, ovs-appctl will wait for ovs-vswitchd to finish -reloading before it exits. + % ovsdb-server /usr/local/etc/ovs-vswitchd.conf.db --remote=punix:/usr/local/var/run/openvswitch/db.sock + +Then initialize the database with "ovs-vsctl init". This is only +necessary the first time after you create the database with +ovsdb-tool (but running it at any time is harmless): + + % ovs-vsctl init + +Then start the main Open vSwitch daemon, telling it to connect to the +same Unix domain socket: + + % ovs-vswitchd unix:/usr/local/var/run/openvswitch/db.sock + +Now you may use ovs-vsctl to set up bridges and other Open vSwitch +features. For example, to create a bridge named br0 and add ports +eth0 and vif1.0 to it: + + % ovs-vsctl add-br br0 + % ovs-vsctl add-port br0 eth0 + % ovs-vsctl add-port br0 vif1.0 + +Please refer to ovs-vsctl(8) for more details. Bug Reporting -------------