Hello Jesse,
> Do you know what type of devices are being attached to OVS (i.e. tap,
> veth, etc.)?
my e-mail has a link to the debug log which contains that Information.
But from my understanding there are several tap devices: one per host,
4-5 per switch. Tap because it needs layer 2.
There are the last commands that are issued before it crashes:
*** Starting controller
*** Starting 4 switches
s1 *** s1 : ('ifconfig lo up',)
*** s1 : ('ovs-vsctl del-br', <OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694> )
*** s1 : ('ovs-vsctl add-br', <OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694> )
*** s1 : ('ovs-vsctl -- set Bridge', <OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694> ,
'other_config:datapath-id=0000000000000001')
*** s1 : ('ovs-vsctl set-fail-mode', <OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694> ,
'secure')
*** s1 : ('ovs-vsctl add-port', <OVSSwitch s1:
lo:127.0.0.1,s1-eth1:None,s1-eth2:None,s1-eth3:None,s1-eth4:None pid=6694> ,
<Intf s1-eth1>)
and than it hangs. I think the last add-port command triggers it.
> Do you know if this happens with an older kernel or with a simpler topology?
No, I don't. I just verified that the Ubuntu Mininet uses the
openvswitch kernel module from openvswitch and not the one that is
shipped with the kernel. Ubuntu precise does not crash with the exact same
topology.
(ubuntu) [~] modinfo openvswitch
filename:
/lib/modules/3.2.0-58-generic/updates/dkms/openvswitch.ko
license: GPL
description: Open vSwitch switching datapath
srcversion: 7CBEB285B79D96D51E0C633
depends:
vermagic: 3.2.0-58-generic SMP mod_unload modversions
Cheers,
Thomas
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
