On Thu, 31 May 2012 23:23:42 +0800
Wenhua Zhang <shiziwen(a)gmail.com> wrote:
Hi Flavio,
Thanks for your help.
I have build the latest net-next kernel and try again.
There is still some problem, and I will try some other method to fix it.
I did those steps yesterday using net-next and I am now running
active-backup on two different machines.
I had to clean the 'configure' caches from libnl and libteam as well
in order to get updated binaries.
fbl
2012/5/31 Flavio Leitner <fbl(a)redhat.com>:
> On Thu, 31 May 2012 11:36:43 +0800
> Wenhua Zhang <shiziwen(a)gmail.com> wrote:
>
>> Hi all,
>> When I try to test the libteam as Example in
>>
https://fedorahosted.org/libteam/wiki/InfrastructureSpecification, I
>> got errors as blew:
>> Failed to create team device.
>> teamd_init() failed.
>> Failed to start daemon: Operation not supported
>>
>> The command is :teamd -f teamd2.conf -D
>> The conf is :
>> {
>> "device": "team0",
>> "runner": {
>> "name": "lacp",
>> "active": 1,
>> "fast_rate": 1
>> },
>> "link_watch": {"name": "ethtool"},
>> "ports": {"eth1": {}, "eth2": {}}
>> }
>>
>> So, is there something wrong with my commands or conf file?
>> Thanks for your help.
>
> You didn't tell what kernel you are using. You need to have
> a kernel with libteam driver enabled.
>
> After booting with that kernel, compile libnl, install it.
> Next compile libteam and install it.
>
> That fixed the same issue here.
> fbl
>