[Ovirt-devel] [PATCH ovirt-appliance] Allow the appliance to manage the hardware it is running on - part 3
Alan Pevec
apevec at redhat.com
Tue Sep 9 00:23:01 UTC 2008
From: Chris Lalancette <clalance at redhat.com>
Since we are currently hardcoding ovirtbr0 in taskomatic,
we have to call the bridge on the host ovirtbr0 to allow guests to start.
This limitation should go away fairly soon with Darryl's network discovery
work, but we need it for now.
Signed-off-by: Chris Lalancette <clalance at redhat.com>
---
create-ovirt-appliance | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/create-ovirt-appliance b/create-ovirt-appliance
index d3800e7..57883e0 100755
--- a/create-ovirt-appliance
+++ b/create-ovirt-appliance
@@ -10,7 +10,7 @@ RAM=768
IMGDIR_DEFAULT=/var/lib/libvirt/images
NAME_DEFAULT=ovirt-appliance
NET_SCRIPTS=/etc/sysconfig/network-scripts
-BRIDGENAME=ovirtbr
+BRIDGENAME=ovirtbr0
imgdir=$IMGDIR_DEFAULT
name=$NAME_DEFAULT
--
1.5.5.1
More information about the ovirt-devel
mailing list