[Ovirt-devel] [PATCH node] Updated the configuration processing to remove the need for scripts.

[Darryl Pierce]

Daniel P. Berrange wrote:
>> +    # now build the list of module aliases to load and load them
>> +    modules=$(awk '/bonding=/ {
>> +            match($0, "bonding=(.*)", data)
>> +            split(data[1], mod, "|")
>> +
>> +            printf("%s ", mod[1])
>> +        }' $CONFIG)
>> +
>> +    /sbin/modprobe $modules
> 
> This is all rather the wrong way to go about setting up bonding, 
> reinventing stuff that's basically done automatically if you
> configure things correctly. For module configuration the only
> thing that should be neccessary is to add
> 
>   alias bond0 bonding
> 
> To '/etc/modprobe.conf' to define a network device bond0. Repeat
> for bond1, bond2, etc as you need.
>
> This causes the neccessary module to be loaded. Everything else
> should then be done in the ifcfg-XXX scripts.



In working on this, doing the above failed every time. The error is:

FATAL: Error inserting bonding
(/lib/modules/2.6.26.5-45.fc9.i686/kernel/drivers/net/bonding/bonding.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

The error from dmesg is:

bonding: Unknown parameter `bond1'

I'm trying to find the URL for it, but the only solution that's worked
is the one in the submitted patch.

-- 
Darryl L. Pierce <dpierce at redhat.com> : GPG KEYID: 6C4E7F1B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dpierce.vcf
Type: text/x-vcard
Size: 319 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20081008/be8dc8bd/attachment.vcf>