From a1a61c8a5bc318a1de81fb9724045f189a0d8b85 Mon Sep 17 00:00:00 2001
From: Maru Newby <mnewby@internap.com>
Date: Wed, 13 Feb 2013 19:20:03 +0000
Subject: [PATCH] Fix name of xen dom0 rootwrap for quantum ovs.

 * Supports blueprint xenapi-ovs

Change-Id: I1d5ac0ce1f226aa3f6c0d7f7bd1eb968aef1eeba
---
 lib/quantum_plugins/openvswitch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/quantum_plugins/openvswitch b/lib/quantum_plugins/openvswitch
index 12bc24422a..181e7e71be 100644
--- a/lib/quantum_plugins/openvswitch
+++ b/lib/quantum_plugins/openvswitch
@@ -75,7 +75,7 @@ function quantum_plugin_configure_plugin_agent() {
         # Nova will always be installed along with quantum for a domU
         # devstack install, so it should be safe to rely on nova.conf
         # for xenapi configuration.
-        Q_RR_DOM0_COMMAND="$QUANTUM_DIR/bin/quantum-rootwrap-dom0 $NOVA_CONF"
+        Q_RR_DOM0_COMMAND="$QUANTUM_DIR/bin/quantum-rootwrap-xen-dom0 $NOVA_CONF"
         # Under XS/XCP, the ovs agent needs to target the dom0
         # integration bridge.  This is enabled by using a root wrapper
         # that executes commands on dom0 via a XenAPI plugin.