File /etc/modprobe.d/dummy.conf ignored on Ubuntu 18.04
With Ubuntu 16.04, I have the following file:
/etc/modprobe.d/dummy.conf
With the following content:
options dummy numdummies=12
And it works fine!
However, with Ubuntu 18.04, this isn't working anymore...
On Bionic, I have to manually run:
rmmod dummy
modprobe dummy numdummies=12
Then, it works!
So, how to do this automatically on Ubuntu 18.04 (new standard)?
Thanks!
networking
asked May 31 '18 at 22:25
ThiagoCMCThiagoCMC
3843922
add a comment |
With Ubuntu 16.04, I have the following file:
/etc/modprobe.d/dummy.conf
With the following content:
options dummy numdummies=12
And it works fine!
However, with Ubuntu 18.04, this isn't working anymore...
On Bionic, I have to manually run:
rmmod dummy
modprobe dummy numdummies=12
Then, it works!
So, how to do this automatically on Ubuntu 18.04 (new standard)?
Thanks!
networking
asked May 31 '18 at 22:25
ThiagoCMCThiagoCMC
3843922
No one knows about this?!
– ThiagoCMC
Jun 1 '18 at 20:57
Looks like a bug... Reported: bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731
– ThiagoCMC
Jun 1 '18 at 21:46
add a comment |
With Ubuntu 16.04, I have the following file:
/etc/modprobe.d/dummy.conf
With the following content:
options dummy numdummies=12
And it works fine!
However, with Ubuntu 18.04, this isn't working anymore...
On Bionic, I have to manually run:
rmmod dummy
modprobe dummy numdummies=12
Then, it works!
So, how to do this automatically on Ubuntu 18.04 (new standard)?
Thanks!
networking
asked May 31 '18 at 22:25
ThiagoCMCThiagoCMC
3843922
With Ubuntu 16.04, I have the following file:
/etc/modprobe.d/dummy.conf
With the following content:
options dummy numdummies=12
And it works fine!
However, with Ubuntu 18.04, this isn't working anymore...
On Bionic, I have to manually run:
rmmod dummy
modprobe dummy numdummies=12
Then, it works!
So, how to do this automatically on Ubuntu 18.04 (new standard)?
Thanks!
networking
networking
asked May 31 '18 at 22:25
ThiagoCMCThiagoCMC
3843922
asked May 31 '18 at 22:25
ThiagoCMCThiagoCMC
3843922
asked May 31 '18 at 22:25
ThiagoCMCThiagoCMC
3843922
asked May 31 '18 at 22:25
ThiagoCMCThiagoCMC
3843922
asked May 31 '18 at 22:25
ThiagoCMCThiagoCMC
3843922
3843922
No one knows about this?!
– ThiagoCMC
Jun 1 '18 at 20:57
Looks like a bug... Reported: bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731
– ThiagoCMC
Jun 1 '18 at 21:46
add a comment |
No one knows about this?!
– ThiagoCMC
Jun 1 '18 at 20:57
Looks like a bug... Reported: bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731
– ThiagoCMC
Jun 1 '18 at 21:46
No one knows about this?!
– ThiagoCMC
Jun 1 '18 at 20:57
No one knows about this?!
– ThiagoCMC
Jun 1 '18 at 20:57
Looks like a bug... Reported: bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731
– ThiagoCMC
Jun 1 '18 at 21:46
Looks like a bug... Reported: bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731
– ThiagoCMC
Jun 1 '18 at 21:46
add a comment |
1 Answer
1
active
oldest
votes
That's not a bug, that's "by design" (although I guess some people would strongly disagree that "design" could be applicable to systemd in general).
As can be seen from this comment, the issue has been tracked down to /lib/modprobe.d/systemd.conf where systemd developers plainly and without a qualm say in comments: "…
When bonding module is loaded, it creates
bond0by default due tomax_bonds
option default value1. This interferes with the network configuration
management / networkd, as it is not possible to detect whether this bond0 was
intentionally configured by the user, or should be managed by
networkd/NM/etc. Therefore disable bond0 creation.options bonding max_bonds=0Do the same fordummy0.
…"
For e. g., if you'd try to modify the module parameter in the way that Ubuntu's documentation cues you'd see that finally modprobe tries to load it so:
…/dummy.ko numdummies=12 numdummies=0
And the latest given arg option effectively overrides its previous occurrences.
answered Jan 23 at 13:59
poigepoige
252111
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1042452%2ffile-etc-modprobe-d-dummy-conf-ignored-on-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
That's not a bug, that's "by design" (although I guess some people would strongly disagree that "design" could be applicable to systemd in general).
As can be seen from this comment, the issue has been tracked down to /lib/modprobe.d/systemd.conf where systemd developers plainly and without a qualm say in comments: "…
When bonding module is loaded, it creates
bond0by default due tomax_bonds
option default value1. This interferes with the network configuration
management / networkd, as it is not possible to detect whether this bond0 was
intentionally configured by the user, or should be managed by
networkd/NM/etc. Therefore disable bond0 creation.options bonding max_bonds=0Do the same fordummy0.
…"
For e. g., if you'd try to modify the module parameter in the way that Ubuntu's documentation cues you'd see that finally modprobe tries to load it so:
…/dummy.ko numdummies=12 numdummies=0
And the latest given arg option effectively overrides its previous occurrences.
answered Jan 23 at 13:59
poigepoige
252111
add a comment |
That's not a bug, that's "by design" (although I guess some people would strongly disagree that "design" could be applicable to systemd in general).
As can be seen from this comment, the issue has been tracked down to /lib/modprobe.d/systemd.conf where systemd developers plainly and without a qualm say in comments: "…
When bonding module is loaded, it creates
bond0by default due tomax_bonds
option default value1. This interferes with the network configuration
management / networkd, as it is not possible to detect whether this bond0 was
intentionally configured by the user, or should be managed by
networkd/NM/etc. Therefore disable bond0 creation.options bonding max_bonds=0Do the same fordummy0.
…"
For e. g., if you'd try to modify the module parameter in the way that Ubuntu's documentation cues you'd see that finally modprobe tries to load it so:
…/dummy.ko numdummies=12 numdummies=0
And the latest given arg option effectively overrides its previous occurrences.
answered Jan 23 at 13:59
poigepoige
252111
add a comment |
That's not a bug, that's "by design" (although I guess some people would strongly disagree that "design" could be applicable to systemd in general).
As can be seen from this comment, the issue has been tracked down to /lib/modprobe.d/systemd.conf where systemd developers plainly and without a qualm say in comments: "…
When bonding module is loaded, it creates
bond0by default due tomax_bonds
option default value1. This interferes with the network configuration
management / networkd, as it is not possible to detect whether this bond0 was
intentionally configured by the user, or should be managed by
networkd/NM/etc. Therefore disable bond0 creation.options bonding max_bonds=0Do the same fordummy0.
…"
For e. g., if you'd try to modify the module parameter in the way that Ubuntu's documentation cues you'd see that finally modprobe tries to load it so:
…/dummy.ko numdummies=12 numdummies=0
And the latest given arg option effectively overrides its previous occurrences.
answered Jan 23 at 13:59
poigepoige
252111
That's not a bug, that's "by design" (although I guess some people would strongly disagree that "design" could be applicable to systemd in general).
As can be seen from this comment, the issue has been tracked down to /lib/modprobe.d/systemd.conf where systemd developers plainly and without a qualm say in comments: "…
When bonding module is loaded, it creates
bond0by default due tomax_bonds
option default value1. This interferes with the network configuration
management / networkd, as it is not possible to detect whether this bond0 was
intentionally configured by the user, or should be managed by
networkd/NM/etc. Therefore disable bond0 creation.options bonding max_bonds=0Do the same fordummy0.
…"
For e. g., if you'd try to modify the module parameter in the way that Ubuntu's documentation cues you'd see that finally modprobe tries to load it so:
…/dummy.ko numdummies=12 numdummies=0
And the latest given arg option effectively overrides its previous occurrences.
answered Jan 23 at 13:59
poigepoige
252111
answered Jan 23 at 13:59
poigepoige
252111
answered Jan 23 at 13:59
poigepoige
252111
answered Jan 23 at 13:59
poigepoige
252111
252111
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1042452%2ffile-etc-modprobe-d-dummy-conf-ignored-on-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
No one knows about this?!
– ThiagoCMC
Jun 1 '18 at 20:57
Looks like a bug... Reported: bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731
– ThiagoCMC
Jun 1 '18 at 21:46