From f5a93d5db152f66da900a81c761874a54e37b540 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Mon, 24 Jul 2017 11:28:04 +0200 Subject: [PATCH] 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. --- README | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README b/README index 2bf8bdc9209..5ae581e338c 100644 --- a/README +++ b/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