diff options
author | 2017-07-24 11:28:04 +0200 | |
---|---|---|
committer | 2017-07-24 11:49:16 +0200 | |
commit | f5a93d5db152f66da900a81c761874a54e37b540 (patch) | |
tree | a3dab2bd50dc310349f016a3fe2ce4c8dd4b247f /README | |
parent | DISTRO_PORTING: document that distros may/should change fallback DNS as well ... (diff) | |
download | systemd-f5a93d5db152f66da900a81c761874a54e37b540.tar.gz systemd-f5a93d5db152f66da900a81c761874a54e37b540.tar.bz2 systemd-f5a93d5db152f66da900a81c761874a54e37b540.zip |
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.
Diffstat (limited to 'README')
-rw-r--r-- | README | 9 |
1 files changed, 9 insertions, 0 deletions
@@ -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 |