ovs version:
# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 2.11.90
DB Schema 8.0.0
linux os:
# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
# uname -r
3.10.0-327.el7.x86_64
when i install openvswitch and start the openvswitch daemon, i found some logs in ovs-vswitch.log:
======
2019-06-14T08:14:01.609Z|00004|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
2019-06-14T08:14:01.609Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
2019-06-14T08:14:01.625Z|00006|dpif_netlink|INFO|The kernel module does not support meters.
2019-06-14T08:14:01.638Z|00007|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on genev_sys_6081 device failed: No such device
2019-06-14T08:14:01.638Z|00008|dpif|WARN|system@ovs-system: port_del failed (No such device)
2019-06-14T08:14:01.638Z|00009|ofproto_dpif|INFO|system@ovs-system: Datapath supports recirculation
2019-06-14T08:14:01.638Z|00010|ofproto_dpif|INFO|system@ovs-system: VLAN header stack length probed as 1
2019-06-14T08:14:01.639Z|00011|ofproto_dpif|INFO|system@ovs-system: MPLS label stack length probed as 1
2019-06-14T08:14:01.639Z|00012|ofproto_dpif|INFO|system@ovs-system: Datapath does not support truncate action
2019-06-14T08:14:01.639Z|00013|ofproto_dpif|INFO|system@ovs-system: Datapath supports unique flow ids
2019-06-14T08:14:01.639Z|00014|ofproto_dpif|INFO|system@ovs-system: Datapath does not support clone action
2019-06-14T08:14:01.639Z|00015|ofproto_dpif|INFO|system@ovs-system: Max sample nesting level probed as 3
2019-06-14T08:14:01.639Z|00016|ofproto_dpif|INFO|system@ovs-system: Datapath does not support eventmask in conntrack action
2019-06-14T08:14:01.639Z|00017|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_clear action
2019-06-14T08:14:01.639Z|00018|ofproto_dpif|INFO|system@ovs-system: Max dp_hash algorithm probed to be 0
2019-06-14T08:14:01.639Z|00019|ofproto_dpif|INFO|system@ovs-system: Datapath does not support check_pkt_len action
2019-06-14T08:14:01.639Z|00020|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_state
2019-06-14T08:14:01.639Z|00021|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_zone
2019-06-14T08:14:01.639Z|00022|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_mark
2019-06-14T08:14:01.639Z|00023|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_label
2019-06-14T08:14:01.639Z|00024|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_state_nat
2019-06-14T08:14:01.639Z|00025|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_orig_tuple
2019-06-14T08:14:01.639Z|00026|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_orig_tuple6
2019-06-14T08:14:01.639Z|00027|dpif_netlink|INFO|dpif_netlink_meter_transact OVS_METER_CMD_SET failed
2019-06-14T08:14:01.639Z|00028|dpif_netlink|INFO|dpif_netlink_meter_transact OVS_METER_CMD_SET failed
2019-06-14T08:14:01.639Z|00029|dpif_netlink|INFO|dpif_netlink_meter_transact get failed
2019-06-14T08:14:01.639Z|00030|dpif_netlink|INFO|The kernel module has a broken meter implementation.
2019-06-14T08:14:01.641Z|00031|bridge|INFO|bridge br-int: added interface 49c38a84c3d5_h on port 28
2019-06-14T08:14:01.642Z|00032|bridge|INFO|bridge br-int: added interface 6f59981aa9e6_h on port 35
==========
anybody can explain the reason?
thanks.
