[libvirt] [PATCH v3 3/3] libvirtd: set openvswitch timeout value based on config data
Since a successful completion of the calls to openvswitch is expected
a longer timeout should be able to be chosen to account for loaded systems.
Therefore this patch provides the ability to specify the timeout value for
openvswitch calls in the libvirtd configuration file.
Signed-off-by: Boris Fiuczynski <fiuczy(a)linux.vnet.ibm.com>
Reviewed-by: Bjoern Walk <bwalk(a)linux.vnet.ibm.com>
---
daemon/libvirtd.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/daemon/libvirtd.c b/daemon/libvirtd.c
index b6d76ed..5c30c9e 100644
--- a/daemon/libvirtd.c
+++ b/daemon/libvirtd.c
@@ -58,6 +58,7 @@
#include "viraccessmanager.h"
#include "virutil.h"
#include "virgettext.h"
+#include "util/virnetdevopenvswitch.h"
#ifdef WITH_DRIVER_MODULES
# include "driver.h"
@@ -658,6 +659,16 @@ daemonSetupNetworking(virNetServerPtr srv,
/*
+ * Set up the openvswitch timeout
+ */
+static void
+daemonSetupNetDevOpenvswitch(struct daemonConfig *config)
+{
+ virNetDevOpenvswitchSetTimeout(config->ovs_timeout);
+}
+
+
+/*
* Set up the logging environment
* By default if daemonized all errors go to the logfile libvirtd.log,
* but if verbose or error debugging is asked for then also output
@@ -1267,6 +1278,8 @@ int main(int argc, char **argv) {
exit(EXIT_FAILURE);
}
+ daemonSetupNetDevOpenvswitch(config);
+
if (daemonSetupAccessManager(config) < 0) {
VIR_ERROR(_("Can't initialize access manager"));
exit(EXIT_FAILURE);
--
2.5.5