[ovs-discuss] (no subject)

[Gurucharan Shetty]

On Thu, Dec 26, 2013 at 6:43 AM, Echedey Lorenzo <echedey at gmail.com> wrote:
> Hi all,
>
> I've been working with Openvswitch for a while now. I hope this is the right
> place to show the problem I'm having after a reboot. I'm using Openvswitch
> 1.9.3 on SLES 11 SP3 and sometimes it does not work while apparently it is
> up&running properly.
>
> I see in /var/log/messages that there was a problema creating the vnet*
> interfaces:
>
> ovs-vswitchd: 00014|netdev_linux|WARN|ethtool command ETHTOOL_GFLAGS on
> network device vnet0 failed: No such device
> ovs-vswitchd: 00015|dpif|WARN|system at virbr0: failed to add vnet0 as port: No
> such device
> ovs-vswitchd: 00016|netdev_linux|WARN|ethtool command ETHTOOL_GFLAGS on
> network device vnet2 failed: No such device
> ovs-vswitchd: 00017|dpif|WARN|system at virbr0: failed to add vnet2 as port: No
> such device
>
I am guessing. It looks to me that vnet0 is a tap interface. i.e., it
is a interface not created by Open vSwitch.
It is possible that when the system is rebooted, ovs-vswitchd which is
a Open vSwitch daemon looks at the OVS database and sees vnet0 as a
port and tries to add it. But since that device does not exist, it
fails to add it.

Who is responsible for the vnet0 creation in your system? Do you see
it in 'ifconfig -a'? It looks to me that whoever is responsible for
its creation is starting after the OVS daemons. You can do a
"/etc/init.d/openvswitch restart" if vnet0 exists and the error should
go away.

> I am not able to see the reason why this happens sometimes. How could I
> debug the origin of this problem? The ovs-vswitchd logs the same
> information.
>
> Thanks,
> Eche
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss
>