The log is probably longer than that, can you provide the whole thing?

On Sun, Feb 22, 2015 at 09:32:39PM +0100, Andrei Manescu wrote:
> Hi Ben,
> 
> Just reproduced it. Booted back to kernel 3.10.0-7 (it’s proxmox) and after 
> setting the switch as netdev, the error appears again. the log does not get 
> updated when I run a command like “ovs-ofctl show vmbr1” but it got populated 
> when I turned the switch to “netdev” device (logs below).
> 
> Let me know what else I can provide.
> 
> Regards,
> Andrei
> 
> root@pve:~# uname -a
> Linux pve 3.10.0-7-pve #1 SMP Thu Jan 22 11:20:00 CET 2015 x86_64 GNU/Linux
> root@pve:~# ovs-ofctl show vmbr1
> OFPT_FEATURES_REPLY (xid=0x2): dpid:0000000c29e93542
> n_tables:254, n_buffers:256
> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
> actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST 
> SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
>  1(eth1): addr:00:0c:29:e9:35:42
>      config:     0
>      state:      0
>      current:    1GB-FD COPPER AUTO_NEG
>      advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
>      supported:  10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
>      speed: 1000 Mbps now, 1000 Mbps max
>  LOCAL(vmbr1): addr:00:0c:29:e9:35:42
>      config:     PORT_DOWN
>      state:      LINK_DOWN
>      speed: 0 Mbps now, 0 Mbps max
> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
> root@pve:~# ovs-ofctl  dump-flows vmbr1 -O OpenFlow13
> OFPST_FLOW reply (OF1.3) (xid=0x2):
>  cookie=0x0, duration=44.442s, table=0, n_packets=76, n_bytes=7595, 
> priority=0 actions=NORMAL
>  cookie=0x0, duration=24.070s, table=0, n_packets=0, n_bytes=0, in_port=5 
> actions=push_mpls:0x8847,set_field:10->mpls_label,output:1
> root@pve:~# ovs-vsctl set bridge vmbr1 datapath_type=netdev
> root@pve:~# ovs-ofctl show vmbr1
> ovs-ofctl: vmbr1 is not a bridge or a socket
> root@pve:~# tail -f /var/log/openvswitch/ovs-
> ovs-ctl.log         ovs-ctl.log.1       ovs-vswitchd.log    ovs-vswitchd.log.1
> root@pve:~# tail -f /var/log/openvswitch/ovs-vswitchd.log
> 2015-02-22T20:29:39.515Z|00019|ofproto_dpif|INFO|netdev@ovs-netdev: Datapath 
> supports recirculation
> 2015-02-22T20:29:39.515Z|00020|ofproto_dpif|INFO|netdev@ovs-netdev: MPLS 
> label stack length probed as 3
> 2015-02-22T20:29:39.516Z|00021|bridge|INFO|bridge vmbr1: added interface 
> vmbr1 on port 65534
> 2015-02-22T20:29:39.516Z|00022|netdev_linux|WARN|vmbr1: obtaining netdev 
> stats via vport failed (No such device)
> 2015-02-22T20:29:39.520Z|00023|bridge|INFO|bridge vmbr1: added interface eth1 
> on port 1
> 2015-02-22T20:29:39.520Z|00024|netdev_linux|WARN|eth1: obtaining netdev stats 
> via vport failed (No such device)
> 2015-02-22T20:29:39.520Z|00025|bridge|INFO|bridge vmbr1: using datapath ID 
> 0000000c29e93542
> 2015-02-22T20:29:39.520Z|00026|connmgr|INFO|vmbr1: added service controller 
> "punix:/var/run/openvswitch/vmbr1.mgmt"
> 2015-02-22T20:29:42.752Z|00027|netdev_linux|WARN|vmbr1: obtaining netdev 
> stats via vport failed (No such device)
> 2015-02-22T20:29:42.752Z|00028|netdev_linux|WARN|eth1: obtaining netdev stats 
> via vport failed (No such device)
> 
> 
> 
> 
> root@pve:~# ls /var/run/openvswitch/vmbr1.mgmt
> ls: cannot access /var/run/openvswitch/vmbr1.mgmt: No such file or directory
> 
> 
> 
> > On 22 Feb 2015, at 00:12, Ben Pfaff <[email protected]> wrote:
> > 
> > On Sat, Feb 21, 2015 at 01:07:34AM +0100, Andrei Manescu wrote:
> >> Hello list,
> >> 
> >> Just started using openvswitch and ran either into a bug or I am missing 
> >> something. According to various mailing list emails, MPLS label operations 
> >> are available in userspace datapath. To configure a vswitch in the 
> >> userspace DP, it needs to be set as a “netdev”, but after doing so, all 
> >> vswitch operational commands fail with "br0 is not a bridge or a socket”. 
> >> 
> >> Found a similar report from back in October: 
> >> http://openvswitch.org/pipermail/discuss/2014-October/015138.html 
> >> <http://openvswitch.org/pipermail/discuss/2014-October/015138.html>, but I 
> >> can’t find if the specified commit made it into 2.3.1 or this is a 
> >> regression bug.
> >> 
> >> Here is the sequence of commands to reproduce (same error for ovs-ofctl 
> >> add-flow):
> >> 
> >> root@pve:~# ovs-vsctl -V
> >> ovs-vsctl (Open vSwitch) 2.3.1
> >> Compiled Dec 27 2014 11:00:30
> >> DB Schema 7.6.2
> >> 
> >> root@pve:~# ovs-vsctl del-br br0
> >> root@pve:~# ovs-vsctl add-br br0
> >> root@pve:~# ovs-vsctl add-port br0 eth1
> >> root@pve:~# ovs-vsctl add-port br0 tap100i0
> >> root@pve:~# ovs-ofctl show br0
> >> OFPT_FEATURES_REPLY (xid=0x2): dpid:0000000c29e93542
> >> n_tables:254, n_buffers:256
> >> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
> >> actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST 
> >> SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
> >> 1(eth1): addr:00:0c:29:e9:35:42
> >>     config:     0
> >>     state:      0
> >>     current:    1GB-FD COPPER AUTO_NEG
> >>     advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
> >>     supported:  10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
> >>     speed: 1000 Mbps now, 1000 Mbps max
> >> 2(tap100i0): addr:ae:6f:8b:e7:50:3a
> >>     config:     0
> >>     state:      0
> >>     current:    10MB-FD COPPER
> >>     speed: 10 Mbps now, 0 Mbps max
> >> LOCAL(br0): addr:00:0c:29:e9:35:42
> >>     config:     PORT_DOWN
> >>     state:      LINK_DOWN
> >>     speed: 0 Mbps now, 0 Mbps max
> >> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
> >> root@pve:~# ovs-vsctl set bridge br0 datapath_type=netdev
> > 
> > What's in the ovs-vswitchd log?
> 


_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to