[Ovirt-devel] [PATCH ovirt-node] Allow the appliance to manage the hardware it is running on - part 3

Alan Pevec apevec at redhat.com
Tue Sep 9 00:21:04 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>
 ovirt-listen-awake/ovirt-convert-host |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/ovirt-listen-awake/ovirt-convert-host b/ovirt-listen-awake/ovirt-convert-host
index 0ef374d..aa9e282 100755
--- a/ovirt-listen-awake/ovirt-convert-host
+++ b/ovirt-listen-awake/ovirt-convert-host
@@ -45,7 +45,7 @@ backup_file /etc/sasl2/libvirt.conf
 backup_file /etc/sysconfig/iptables
-/usr/sbin/lokkit -n -t ovirtbr
+/usr/sbin/lokkit -n -t ovirtbr0
 echo "Setup complete.  To make the changes take effect, shut down any running
 guests and reboot the host"

More information about the ovirt-devel mailing list