mirror of
https://github.com/systemd/systemd.git
synced 2024-12-22 17:35:35 +03:00
README: document that max_bonds=0 is the way to go for bonding.ko
Everything else just is annoying, hence let's list this among the requirements we make on the kernel in order to minimize confusion leading to #6184 and suchlike.
This commit is contained in:
parent
0629976f08
commit
f5a93d5db1
9
README
9
README
@ -107,6 +107,15 @@ REQUIREMENTS:
|
||||
fixed, and it's best to disable group scheduling hence.
|
||||
CONFIG_RT_GROUP_SCHED=n
|
||||
|
||||
It's a good idea to disable the implicit creation of networking bonding
|
||||
devices by the kernel networking bonding module, so that the
|
||||
automatically created "bond0" interface doesn't conflict with any such
|
||||
device created by systemd-networkd (or other tools). Please make sure
|
||||
that the kernel module bonding.ko is shipped with max_bonds=0 set by
|
||||
default. Ideally there would be a kernel compile-time option for this,
|
||||
but there currently isn't. The next best thing is to make this change
|
||||
through a modprobe.d drop-in.
|
||||
|
||||
Note that kernel auditing is broken when used with systemd's
|
||||
container code. When using systemd in conjunction with
|
||||
containers, please make sure to either turn off auditing at
|
||||
|
Loading…
Reference in New Issue
Block a user