On Wed, Oct 09, 2013 at 12:28:58PM +0530, nisha goyal wrote: > I figured out that the problem is that the ovs is not able to write the > configurations for the VMs into its db. Please refer to the excerpts from > the ovs-vswitchd.log file: > > Oct 07 15:18:54|00031|bridge|INFO|created port br0 on bridge br0 > Oct 07 15:18:54|00032|ofproto|INFO|using datapath ID 0000002320de1035 > Oct 07 15:18:54|00033|bridge|WARN|bridge br0: using default bridge Ethernet > address X:X:X:X:X:X > Oct 07 15:18:54|00034|ofproto|INFO|datapath ID changed to 00000e59d5807d4f > Oct 07 15:18:54|00035|bridge|INFO|created port eth0 on bridge br0 > Oct 07 15:18:54|00036|ofproto|INFO|datapath ID changed to 0000545200011788 > Oct 07 15:19:52|00037|bridge|INFO|created port vlan10 on bridge br0 > Oct 07 15:19:52|00038|netdev_linux|WARN|/sys/class/net/vnet0/carrier: open > failed: No such file or directory > Oct 07 15:20:05|00039|bridge|INFO|created port vlan20 on bridge br0 > Oct 07 15:20:05|00040|netdev_linux|WARN|/sys/class/net/vnet1/carrier: open > failed: No such file or directory > Oct 07 15:22:58|00041|bridge|INFO|destroyed port eth0 on bridge br0 > > > There are no datapath IDs created for vnet0, vnet1 and so on. Can you > please tell me, what could be the possible cause for it?
I think that you are misinterpreting the output. Datapath ID is a property of a bridge, not a port, so it is no surprise that there is no mention of it on a per-port basis. The messages about /sys/class/net/vnet0/carrier and /sys/class/net/vnet1/carrier are more interesting. They imply that no network devices named vnet0 or vnet1 exist. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
