[Ovirt-devel] [PATCH server] Replaced the config scripts with configuration encoding.

[Daniel P. Berrange]

On Tue, Oct 14, 2008 at 11:38:51AM -0400, Darryl L. Pierce wrote:
> A line that begins with "kmod" describes a kernel module that
> needs to be loaded. It will containing the module's name, an
> optional alias for the module, and then the module options
> if such are required.

This is wrong - module options for bonding are per-NIC.

> +# kmod=[module name]|[module alias]|[module options]
> +#
> +# An example would be for loading the +bonding+ kernel module to setup a bonded
> +# interface for load balancing. In this example, the bonded interface would be
> +# named +failover0+ on the node:
> +#
> +# kmod=bonding|failover0|mode=2 miimon=100 downdelay=200

This options must be set against the NIC, not the module

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|