[DPTECH-Developer-Shell]cat /proc/version Linux version 2.6.32.9 (root@ubuntu-soft) (gcc version 4.4.7 (GCC) ) #8 SMP Fri Mar 18 04:17:22 CST 2016 [DPTECH-Developer-Shell]
Best regards, Yugang yugang 发件人： Chandran, Sugesh 发送时间： 2016-03-22 21:34 收件人： yugang; yugangdeai; discuss 主题： RE: 回复: [ovs-discuss] userspace openvswitch What kernel version are you using?? Regards _Sugesh From: yugang [mailto:yug...@dptechnology.net] Sent: Tuesday, March 22, 2016 3:38 AM To: Chandran, Sugesh <sugesh.chand...@intel.com>; yugangdeai <yugangd...@163.com>; discuss <discuss@openvswitch.org> Subject: 回复: 回复: [ovs-discuss] userspace openvswitch yugang 发件人： yugang 发送时间： 2016-03-22 11:23 收件人： Chandran, Sugesh; yugangdeai; discuss 主题： 回复: 回复: [ovs-discuss] userspace openvswitch Dear, Here are more logs [DPTECH-Developer-Shell]cat /usr/local/var/log/openvswitch/ovs-vswitchd.log|grep ERR 2008-12-31T21:10:05.326Z|00041|bridge|ERR|failed to create bridge br0: Unknown error 1072477328 2008-12-31T21:10:12.711Z|00061|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:12.712Z|00062|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:30.195Z|00075|bridge|ERR|failed to create bridge br0: Unknown error 1072477328 2008-12-31T21:10:30.196Z|00076|bridge|ERR|failed to create bridge br1: Unknown error 1072477328 2008-12-31T21:10:42.711Z|00083|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:42.711Z|00084|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:43.147Z|00095|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:43.147Z|00096|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:47.646Z|00105|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:47.646Z|00106|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:51.267Z|00116|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:51.267Z|00117|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:52.384Z|00126|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:10:52.385Z|00127|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:11:00.811Z|00136|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:11:00.811Z|00137|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:11:42.711Z|00159|socket_util|ERR|Dropped 2 log messages in last 32 seconds (most recently, 32 seconds ago) due to excessive rate 2008-12-31T21:11:42.712Z|00160|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:11:42.712Z|00161|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:12:13.539Z|00179|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:12:13.539Z|00180|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:12:13.592Z|00189|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:12:13.593Z|00190|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:12:38.182Z|00219|socket_util|ERR|Dropped 4 log messages in last 20 seconds (most recently, 15 seconds ago) due to excessive rate 2008-12-31T21:12:38.183Z|00220|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:12:38.184Z|00221|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:12:50.908Z|00230|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:13:12.721Z|00249|socket_util|ERR|Dropped 3 log messages in last 21 seconds (most recently, 19 seconds ago) due to excessive rate 2008-12-31T21:13:12.722Z|00250|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:13:12.723Z|00251|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:13:32.240Z|00268|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:13:42.721Z|00278|socket_util|ERR|Dropped 1 log messages in last 10 seconds (most recently, 10 seconds ago) due to excessive rate 2008-12-31T21:13:42.722Z|00279|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:13:56.974Z|00290|socket_util|ERR|Dropped 1 log messages in last 15 seconds (most recently, 15 seconds ago) due to excessive rate 2008-12-31T21:13:56.975Z|00291|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:14:06.754Z|00309|socket_util|ERR|Dropped 3 log messages in last 9 seconds (most recently, 8 seconds ago) due to excessive rate 2008-12-31T21:14:06.755Z|00310|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:14:12.720Z|00327|socket_util|ERR|Dropped 3 log messages in last 6 seconds (most recently, 2 seconds ago) due to excessive rate 2008-12-31T21:14:12.721Z|00328|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T21:15:13.731Z|00002|daemon_unix|ERR|fork child died before signaling startup (killed (Segmentation fault), core dumped) 2008-12-31T23:29:12.408Z|00052|bridge|ERR|failed to create bridge br12: Address family not supported by protocol 2008-12-31T23:29:12.411Z|00055|bridge|ERR|failed to create bridge br2: Address family not supported by protocol 2008-12-31T23:29:12.414Z|00058|bridge|ERR|failed to create bridge br0: Address family not supported by protocol 2008-12-31T23:29:12.417Z|00061|bridge|ERR|failed to create bridge br133: Address family not supported by protocol 2008-12-31T23:29:16.420Z|00064|bridge|ERR|failed to create bridge br1: Address family not supported by protocol 2008-12-31T23:29:18.266Z|00093|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:29:18.266Z|00094|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:29:20.036Z|00109|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:29:20.037Z|00110|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:29:37.264Z|00130|bridge|ERR|failed to create bridge br12: Address family not supported by protocol 2008-12-31T23:29:37.267Z|00133|bridge|ERR|failed to create bridge br2: Address family not supported by protocol 2008-12-31T23:29:37.268Z|00136|bridge|ERR|failed to create bridge br0: Address family not supported by protocol 2008-12-31T23:29:37.269Z|00139|bridge|ERR|failed to create bridge br1: Address family not supported by protocol 2008-12-31T23:29:37.270Z|00142|bridge|ERR|failed to create bridge br1666: Address family not supported by protocol 2008-12-31T23:29:37.270Z|00145|bridge|ERR|failed to create bridge br133: Address family not supported by protocol 2008-12-31T23:29:48.269Z|00151|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:29:48.269Z|00152|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:15.769Z|00162|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:15.769Z|00163|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:15.825Z|00172|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:15.826Z|00173|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:18.271Z|00186|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:18.272Z|00187|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:48.493Z|00196|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:48.494Z|00197|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:49.268Z|00213|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:30:49.269Z|00214|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:31:18.791Z|00223|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:31:18.792Z|00224|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:31:18.848Z|00233|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:31:18.849Z|00234|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:31:48.469Z|00261|socket_util|ERR|Dropped 4 log messages in last 25 seconds (most recently, 25 seconds ago) due to excessive rate 2008-12-31T23:31:48.470Z|00262|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:31:48.470Z|00263|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:32:18.468Z|00274|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:32:18.469Z|00275|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:32:24.065Z|00290|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:32:34.739Z|00300|socket_util|ERR|Dropped 1 log messages in last 10 seconds (most recently, 10 seconds ago) due to excessive rate 2008-12-31T23:32:34.740Z|00301|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:33:18.472Z|00310|socket_util|ERR|Dropped 1 log messages in last 44 seconds (most recently, 44 seconds ago) due to excessive rate 2008-12-31T23:33:18.473Z|00311|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:33:18.473Z|00312|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:33:33.067Z|00322|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:33:33.068Z|00323|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:33:43.211Z|00333|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:33:43.212Z|00334|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:34:18.476Z|00363|socket_util|ERR|Dropped 4 log messages in last 33 seconds (most recently, 33 seconds ago) due to excessive rate 2008-12-31T23:34:18.477Z|00364|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:34:18.477Z|00365|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:34:36.388Z|00381|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:34:36.389Z|00382|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:34:48.624Z|00392|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:35:18.478Z|00405|socket_util|ERR|Dropped 1 log messages in last 30 seconds (most recently, 30 seconds ago) due to excessive rate 2008-12-31T23:35:18.479Z|00406|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:35:18.479Z|00407|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:35:34.131Z|00417|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:35:34.132Z|00418|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:35:48.686Z|00427|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:36:18.678Z|00451|socket_util|ERR|Dropped 3 log messages in last 30 seconds (most recently, 29 seconds ago) due to excessive rate 2008-12-31T23:36:18.678Z|00452|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:36:18.678Z|00453|socket_util|ERR|getsockopt(SO_PROTOCOL): Protocol not available 2008-12-31T23:37:44.313Z|00002|daemon_unix|ERR|fork child died before signaling startup (killed (Segmentation fault), core dumped) 2009-01-02T14:42:35.390Z|00056|dpif_netlink|ERR|Generic Netlink family 'ovs_datapath' does not exist. The Open vSwitch kernel module is probably not loaded. 2009-01-02T14:42:35.393Z|00059|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:35.394Z|00060|ofproto|ERR|failed to open datapath br1008: No such file or directory 2009-01-02T14:42:35.395Z|00061|bridge|ERR|failed to create bridge br1008: No such file or directory 2009-01-02T14:42:39.397Z|00064|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:39.398Z|00065|ofproto|ERR|failed to open datapath br1009: No such file or directory 2009-01-02T14:42:39.399Z|00066|bridge|ERR|failed to create bridge br1009: No such file or directory 2009-01-02T14:42:39.415Z|00069|ofproto_dpif|ERR|failed to open datapath of type netdev: Invalid argument 2009-01-02T14:42:39.416Z|00070|ofproto|ERR|failed to open datapath brtest: Invalid argument 2009-01-02T14:42:39.417Z|00071|bridge|ERR|failed to create bridge brtest: Invalid argument 2009-01-02T14:42:39.419Z|00074|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:39.420Z|00075|ofproto|ERR|failed to open datapath br1007: No such file or directory 2009-01-02T14:42:39.420Z|00076|bridge|ERR|failed to create bridge br1007: No such file or directory 2009-01-02T14:42:39.424Z|00079|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:39.425Z|00080|ofproto|ERR|failed to open datapath br000: No such file or directory 2009-01-02T14:42:39.426Z|00081|bridge|ERR|failed to create bridge br000: No such file or directory 2009-01-02T14:42:39.429Z|00084|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:39.430Z|00085|ofproto|ERR|failed to open datapath br1005: No such file or directory 2009-01-02T14:42:39.431Z|00086|bridge|ERR|failed to create bridge br1005: No such file or directory 2009-01-02T14:42:39.447Z|00089|ofproto_dpif|ERR|failed to open datapath of type netdev: Invalid argument 2009-01-02T14:42:39.448Z|00090|ofproto|ERR|failed to open datapath br11: Invalid argument 2009-01-02T14:42:39.449Z|00091|bridge|ERR|failed to create bridge br11: Invalid argument 2009-01-02T14:42:39.451Z|00094|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:39.452Z|00095|ofproto|ERR|failed to open datapath testbridge: No such file or directory 2009-01-02T14:42:39.452Z|00096|bridge|ERR|failed to create bridge testbridge: No such file or directory 2009-01-02T14:42:39.453Z|00099|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:39.454Z|00100|ofproto|ERR|failed to open datapath br1010: No such file or directory 2009-01-02T14:42:43.444Z|00101|bridge|ERR|failed to create bridge br1010: No such file or directory 2009-01-02T14:42:43.445Z|00104|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:43.446Z|00105|ofproto|ERR|failed to open datapath br1006: No such file or directory 2009-01-02T14:42:43.446Z|00106|bridge|ERR|failed to create bridge br1006: No such file or directory 2009-01-02T14:42:43.448Z|00109|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:43.448Z|00110|ofproto|ERR|failed to open datapath br1004: No such file or directory 2009-01-02T14:42:43.448Z|00111|bridge|ERR|failed to create bridge br1004: No such file or directory 2009-01-02T14:42:43.453Z|00114|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:43.454Z|00115|ofproto|ERR|failed to open datapath br0: No such file or directory 2009-01-02T14:42:43.454Z|00116|bridge|ERR|failed to create bridge br0: No such file or directory 2009-01-02T14:42:43.485Z|00119|ofproto_dpif|ERR|failed to open datapath of type netdev: Invalid argument 2009-01-02T14:42:43.486Z|00120|ofproto|ERR|failed to open datapath brtest1: Invalid argument 2009-01-02T14:42:43.487Z|00121|bridge|ERR|failed to create bridge brtest1: Invalid argument [DPTECH-Developer-Shell] Best regards, Yugang yugang 发件人： yugang 发送时间： 2016-03-22 09:11 收件人： Chandran, Sugesh; yugangdeai; discuss 主题： 回复: Re: [ovs-discuss] userspace openvswitch Dear, Here are the log: 2009-01-02T14:42:35Z|00043|hmap|DBG|lib/shash.c:112: 6 nodes in bucket (64 nodes, 32 buckets) 2009-01-02T14:42:35Z|00044|hmap|DBG|lib/shash.c:112: 6 nodes in bucket (64 nodes, 32 buckets) 2009-01-02T14:42:35Z|00045|netlink_socket|DBG|nl_sock_send__ (Success): nl(len:17, type=26(family-defined), flags=305[REQUEST][ACK][DUMP], seq=1, pid=4294963102 2009-01-02T14:42:35Z|00046|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:68, type=24(family-defined), flags=2[MULTI], seq=1, pid=4294963102 2009-01-02T14:42:35Z|00047|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:164, type=24(family-defined), flags=2[MULTI], seq=1, pid=4294963102 2009-01-02T14:42:35Z|00048|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:164, type=24(family-defined), flags=2[MULTI], seq=1, pid=4294963102 2009-01-02T14:42:35Z|00049|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:144, type=24(family-defined), flags=2[MULTI], seq=1, pid=4294963102 2009-01-02T14:42:35Z|00050|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:144, type=24(family-defined), flags=2[MULTI], seq=1, pid=4294963102 2009-01-02T14:42:35Z|00051|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:144, type=24(family-defined), flags=2[MULTI], seq=1, pid=4294963102 2009-01-02T14:42:35Z|00052|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:20, type=3(done), flags=2[MULTI], seq=1, pid=4294963102 done(0) 2009-01-02T14:42:35Z|00053|netlink_socket|DBG|nl_sock_transact_multiple__ (Success): nl(len:40, type=16(control), flags=1[REQUEST], seq=1, pid=14940,genl(cmd=3,version=1) 2009-01-02T14:42:35Z|00054|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:36, type=2(error), flags=0, seq=1, pid=14940 error(-2(No such file or directory), in-reply-to(nl(len:40, type=16(control), flags=1[REQUEST], seq=1, pid=14940)) 2009-01-02T14:42:35Z|00055|netlink_socket|DBG|received NAK error=0 (No such file or directory) 2009-01-02T14:42:35Z|00056|dpif_netlink|ERR|Generic Netlink family 'ovs_datapath' does not exist. The Open vSwitch kernel module is probably not loaded. 2009-01-02T14:42:35Z|00057|dpif|WARN|failed to enumerate system datapaths: No such file or directory 2009-01-02T14:42:35Z|00058|dpif|WARN|failed to create datapath ovs-system: No such file or directory 2009-01-02T14:42:35Z|00059|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:35Z|00060|ofproto|ERR|failed to open datapath br1008: No such file or directory 2009-01-02T14:42:35Z|00061|bridge|ERR|failed to create bridge br1008: No such file or directory 2009-01-02T14:42:35Z|00062|dpif|WARN|failed to enumerate system datapaths: No such file or directory 2009-01-02T14:42:39Z|00063|dpif|WARN|failed to create datapath ovs-system: No such file or directory 2009-01-02T14:42:39Z|00064|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory 2009-01-02T14:42:39Z|00065|ofproto|ERR|failed to open datapath br1009: No such file or directory 2009-01-02T14:42:39Z|00066|bridge|ERR|failed to create bridge br1009: No such file or directory 2009-01-02T14:42:39Z|00067|netdev_linux|WARN|ovs-netdev: creating tap device failed: Invalid argument Best regards, Yugang yugang 发件人： yugang 发送时间： 2016-03-22 09:03 收件人： Chandran, Sugesh; yugangdeai; discuss 主题： Re: RE: [ovs-discuss] userspace openvswitch We have checked ‘INSTALL.userspace.md’ , it's same as version 1.11.0, and on the same device, version 1.11.0 is ok, here are tun module information: [DPTECH-Developer-Shell]mknod /dev/net/tun c 10 200 [DPTECH-Developer-Shell]ls /dev/net tun [DPTECH-Developer-Shell]ls /dev/net -l total 0 crw-r--r-- 1 root root 10, 200 Jan 2 22:39 tun [DPTECH-Developer-Shell] Best regards, Yugang yugang From: Chandran, Sugesh Date: 2016-03-21 18:31 To: yugang; yugangdeai; discuss Subject: RE: RE: [ovs-discuss] userspace openvswitch Regards _Sugesh From: yugang [mailto:yug...@dptechnology.net] Sent: Monday, March 21, 2016 9:40 AM To: Chandran, Sugesh <sugesh.chand...@intel.com>; yugangdeai <yugangd...@163.com>; discuss <discuss@openvswitch.org> Subject: Re: RE: [ovs-discuss] userspace openvswitch [DPTECH-Developer-Shell]ovs-vsctl --timeout 10 add-br brtest -- set bridge brtes t datapath_type=netdev ovs-vsctl: Error detected while setting up 'brtest'. See ovs-vswitchd log for details. [DPTECH-Developer-Shell] We can also ignore this error msg? [Sugesh] No, You are not supposed to get this error. Have you looked at ovs logs??Please have a look at ‘INSTALL.userspace.md’ for detailed guide on how to set up OVS in userspace. You might need to load tun/tap kernel module for creating the bridge. yugang From: Chandran, Sugesh Date: 2016-03-21 17:03 To: yugang; yugangdeai; discuss Subject: RE: Re: [ovs-discuss] userspace openvswitch Specify the type of bridge as netdev for userspace bridge. ovs-vsctl --timeout 10 add-br br0 -- set bridge br0 datapath_type=netdev You can ignore the warning message “failed to enumerate ….” for now. Verify if the bridge has been created successfully using ‘ovs-vsctl show’. Regards _Sugesh From: yugang [mailto:yug...@dptechnology.net] Sent: Monday, March 21, 2016 8:57 AM To: Chandran, Sugesh <sugesh.chand...@intel.com>; yugangdeai <yugangd...@163.com>; discuss <discuss@openvswitch.org> Subject: Re: Re: [ovs-discuss] userspace openvswitch if it does, why i can add bridge with tool ovs-vsctl on version 1.11.0, but failed on the latest version, [Sugesh] What error you are getting? [DPTECH-Developer-Shell]ps aux|grep ovs root 4289 0.4 0.2 5904 1976 ? Ss 04:13 0:41 ./ovs-vswitchd --pidfile --detach --verbose root 9744 0.0 0.0 2088 340 ttyS0 S+ 06:33 0:00 grep ovs root 24785 0.0 0.1 3924 1460 ? Ss Jan01 0:19 ovsdb-server -v --remote=punix:/usr/local/var/run/openvswitch/db.sock --remote=db:Open_vSwitch,Open_vSwitch,manager_options --private-key=db:Open_vSwitch,SSL,private_key --certificate=db:Open_vSwitch,SSL,certificate --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --pidfile --detach --log-file [DPTECH-Developer-Shell] [DPTECH-Developer-Shell]ovs-vsctl add-br testbridge ovs-vsctl: Error detected while setting up 'testbridge'. See ovs-vswitchd log for details. [DPTECH-Developer-Shell] Here are more: 2009-01-01T20:13:36Z|00051|netlink_socket|DBG|nl_sock_recv__ (Success): nl(len:36, type=2(error), flags=0, seq=1, pid=4289 error(-2(No such file or directory), in-reply-to(nl(len:40, type=16(control), flags=1[REQUEST], seq=1, pid=4289)) 2009-01-01T20:13:36Z|00052|netlink_socket|DBG|received NAK error=0 (No such file or directory) 2009-01-01T20:13:36Z|00053|dpif_netlink|ERR|Generic Netlink family 'ovs_datapath' does not exist. The Open vSwitch kernel module is probably not loaded. 2009-01-01T20:13:36Z|00054|dpif|WARN|failed to enumerate system datapaths: No such file or directory 2009-01-01T20:13:36Z|00055|dpif|WARN|failed to create datapath ovs-system: No such file or directory 2009-01-01T20:13:36Z|00056|ofproto_dpif|ERR|failed to open datapath of type system: No such file or directory Best regards, Yugang yugang From: Chandran, Sugesh Date: 2016-03-21 16:42 To: shanghai; discuss@openvswitch.org Subject: Re: [ovs-discuss] userspace openvswitch Regards _Sugesh From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of shanghai Sent: Sunday, March 20, 2016 8:26 AM To: discuss@openvswitch.org Subject: [ovs-discuss] userspace openvswitch Dear there, Thanks for your time, i want to know that whether the version 2.5.0 openvswitch can work in userspace totaly, [Sugesh] 2.5.0 supports userspace datapath. if it does, why i can add bridge with tool ovs-vsctl on version 1.11.0, but failed on the latest version, [Sugesh] What error you are getting? which remind me to load the kernel module, how could i solve this problem. I am really looking forward to hear from you. [Sugesh] No need to load ovs kernel module for userspace datapath. Best regards, Yugang .
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
