[ovs-dev] ovs-vswitchd start order on debian

Dietmar Maurer dietmar at proxmox.com
Thu Dec 19 06:49:50 UTC 2013


I am testing latest ovs code on debian, using the following /etc/network/interfaces

-------------------
allow-vmbr0 eth1
iface eth1 inet manual
	ovs_type OVSPort
	ovs_bridge vmbr0

auto vmbr0
allow-ovs vmbr0
iface vmbr0 inet static
	address  192.168.2.8
	netmask  255.255.240.0
	gateway  192.168.2.1
	ovs_type OVSBridge
	ovs_ports eth1

------------------

That works, but it does not work when I boot the host. Simply because ovs-vswitchd
is started much too late in runlevel 2.

So what is the reasoning behind that? 

I also tested with modified values in /etc/init.d/openvswitch-switch using something like:

# X-Start-Before:    networking
# X-Stop-After:      networking
# Default-Start:     S
# Default-Stop:      0 6

That solves the problem, but does that have some bad side effects? 
(For example syslog is not active at that time.)





More information about the dev mailing list