I have a KVM domain which libvirt cannot start when the KVM host boot due to the fact that the network bridge is not yet started. It takes a while before the bridge is up, about 10-20 seconds.
One solution is to change that libvirt bin shall wait for the bridge before starting, but all instructions about that assumes a startup job, but libvirt-bin startup is a common init-script.
How do I solve this problem? The bridge name is br2.
Using ubuntu 14.04
One solution is to change that libvirt bin shall wait for the bridge before starting, but all instructions about that assumes a startup job, but libvirt-bin startup is a common init-script.
PHP Code:
#! /bin/sh
#
# Init script for libvirtd
#
# (c) 2007 Guido Guenther <agx@sigxcpu.org>
# based on the skeletons that comes with dh_make
#
### BEGIN INIT INFO
# Provides: libvirt-bin libvirtd
# Required-Start: $network $local_fs $remote_fs $syslog
# Required-Stop: $local_fs $remote_fs $syslog
# Should-Start: hal avahi cgconfig
# Should-Stop: hal avahi cgconfig
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: libvirt management daemon
### END INIT INFO
Using ubuntu 14.04