Hey folks -
I'm at a bit of a loss here. My Ubuntu server is running KVM with several VMs. I'm also making use of OpenVSwitch for the VMs' networking. The challenge that I'm running into is the run order of processes on the hypervisor. I need the openvswitch-controller and openvswitch-switch init scripts to start before the libvirt management daemon. By default, they start after libvirt, and only 1 of my VMs will auto-start given the unavailability of the VSwitch.
I can reproduce this at will by killing the VSwitch processes and then trying to start one of the VMs. It won't go. As soon as the VSwitch processes are running, it starts right up.
The openvswitch init scripts are linked to /etc/rc3.d as I'd expect (with an S20... prefix). But libvirt's init script is nowhere to be found. How's it started upon machine boot? How do I force it to wait until the openvswitch daemons are running?
Thanks!
I'm at a bit of a loss here. My Ubuntu server is running KVM with several VMs. I'm also making use of OpenVSwitch for the VMs' networking. The challenge that I'm running into is the run order of processes on the hypervisor. I need the openvswitch-controller and openvswitch-switch init scripts to start before the libvirt management daemon. By default, they start after libvirt, and only 1 of my VMs will auto-start given the unavailability of the VSwitch.
I can reproduce this at will by killing the VSwitch processes and then trying to start one of the VMs. It won't go. As soon as the VSwitch processes are running, it starts right up.
The openvswitch init scripts are linked to /etc/rc3.d as I'd expect (with an S20... prefix). But libvirt's init script is nowhere to be found. How's it started upon machine boot? How do I force it to wait until the openvswitch daemons are running?
Thanks!