X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=INSTALL.Linux;h=c0b07d528598d61724a981f57564f91903c2d7a9;hb=9b80f761bed9a32c1b0eb22ee3361966057ea973;hp=8ef2315777f7850ef29613378cd81ec3e06d48d2;hpb=897a8e0791171c8cb71e27c31d159a08205e5741;p=sliver-openvswitch.git diff --git a/INSTALL.Linux b/INSTALL.Linux index 8ef231577..c0b07d528 100644 --- a/INSTALL.Linux +++ b/INSTALL.Linux @@ -120,7 +120,7 @@ following software: You should ensure that /dev/urandom exists. To support TAP devices, you must also ensure that /dev/net/tun exists. -To run the ovsdmonitor tool, the machine must also have the following +To run the ovsdbmonitor tool, the machine must also have the following software: - Python 2.x, for x >= 4. @@ -194,16 +194,16 @@ Prerequisites section, follow the procedure below to build. 6. If you built kernel modules, you may load them with "insmod", e.g.: - % insmod datapath/linux/openvswitch_mod.ko + % insmod datapath/linux/openvswitch.ko You may need to specify a full path to insmod, e.g. /sbin/insmod. To verify that the modules have been loaded, run "/sbin/lsmod" and - check that openvswitch_mod is listed. + check that openvswitch is listed. If the "insmod" operation fails, look at the last few kernel log messages (e.g. with "dmesg | tail"): - - The message "openvswitch_mod: exports duplicate symbol + - The message "openvswitch: exports duplicate symbol br_should_route_hook (owned by bridge)" means that the bridge module is loaded. Run "/sbin/rmmod bridge" to remove it. @@ -212,7 +212,7 @@ Prerequisites section, follow the procedure below to build. the kernel, rather than as a module. Open vSwitch does not support this configuration (see "Build Requirements", above). - - The message "openvswitch_mod: exports duplicate symbol + - The message "openvswitch: exports duplicate symbol dp_ioctl_hook (owned by ofdatapath)" means that the ofdatapath module from the OpenFlow reference implementation is loaded. Run "/sbin/rmmod ofdatapath" to remove it. (You might have to @@ -222,10 +222,10 @@ Prerequisites section, follow the procedure below to build. - Otherwise, the most likely problem is that Open vSwitch was built for a kernel different from the one into which you are - trying to load it. Run "modinfo" on openvswitch_mod.ko and on + trying to load it. Run "modinfo" on openvswitch.ko and on a module built for the running kernel, e.g.: - % /sbin/modinfo openvswitch_mod.ko + % /sbin/modinfo openvswitch.ko % /sbin/modinfo /lib/modules/`uname -r`/kernel/net/bridge/bridge.ko Compare the "vermagic" lines output by the two commands. If @@ -235,7 +235,7 @@ Prerequisites section, follow the procedure below to build. module loading, please include the output from the "dmesg" and "modinfo" commands mentioned above. - There is an optional module parameter to openvswitch_mod.ko called + There is an optional module parameter to openvswitch.ko called vlan_tso that enables TCP segmentation offload over VLANs on NICs that support it. Many drivers do not expose support for TSO on VLANs in a way that Open vSwitch can use but there is no way to detect