VMPlayer doesn't load modules anymore
I'm struggeling with my VMWare Workstation.
Environment: Kubuntu 18.10 with Kernel 4.18.0-12-generic on a Lenovo Thinkpad
Situation: While the notebook runs with kernel version 4.18.0-11-generic, I can start vmplayer, it compiles (if needed) its kernel module (vmmon.ko and vmnet.ko) and then starts the virtual machine without any problem.
After updating to kernel version 4.18.0-12-generic, vmplayer compiles again both modules, however the modules cannot be loaded anymore. Loading the modules manually leads to the following error message:
root@koehn-ThinkPad# modprobe -v vmmon
insmod /lib/modules/4.18.0-12-generic/misc/vmmon.ko
modprobe: ERROR: could not insert 'vmmon': Operation not permitted
If I reboot the system and start again 4.18.0-11-generic, everything is fine again.
Does anybody have an idea?
BTW, I also tried 4.18.0-13-generic. The result is identical to -12.
drivers kernel vmware 18.10
asked Jan 12 at 17:00
MartinMartin
31
New contributor
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I'm struggeling with my VMWare Workstation.
Environment: Kubuntu 18.10 with Kernel 4.18.0-12-generic on a Lenovo Thinkpad
Situation: While the notebook runs with kernel version 4.18.0-11-generic, I can start vmplayer, it compiles (if needed) its kernel module (vmmon.ko and vmnet.ko) and then starts the virtual machine without any problem.
After updating to kernel version 4.18.0-12-generic, vmplayer compiles again both modules, however the modules cannot be loaded anymore. Loading the modules manually leads to the following error message:
root@koehn-ThinkPad# modprobe -v vmmon
insmod /lib/modules/4.18.0-12-generic/misc/vmmon.ko
modprobe: ERROR: could not insert 'vmmon': Operation not permitted
If I reboot the system and start again 4.18.0-11-generic, everything is fine again.
Does anybody have an idea?
BTW, I also tried 4.18.0-13-generic. The result is identical to -12.
drivers kernel vmware 18.10
asked Jan 12 at 17:00
MartinMartin
31
New contributor
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I'm struggeling with my VMWare Workstation.
Environment: Kubuntu 18.10 with Kernel 4.18.0-12-generic on a Lenovo Thinkpad
Situation: While the notebook runs with kernel version 4.18.0-11-generic, I can start vmplayer, it compiles (if needed) its kernel module (vmmon.ko and vmnet.ko) and then starts the virtual machine without any problem.
After updating to kernel version 4.18.0-12-generic, vmplayer compiles again both modules, however the modules cannot be loaded anymore. Loading the modules manually leads to the following error message:
root@koehn-ThinkPad# modprobe -v vmmon
insmod /lib/modules/4.18.0-12-generic/misc/vmmon.ko
modprobe: ERROR: could not insert 'vmmon': Operation not permitted
If I reboot the system and start again 4.18.0-11-generic, everything is fine again.
Does anybody have an idea?
BTW, I also tried 4.18.0-13-generic. The result is identical to -12.
drivers kernel vmware 18.10
asked Jan 12 at 17:00
MartinMartin
31
New contributor
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I'm struggeling with my VMWare Workstation.
Environment: Kubuntu 18.10 with Kernel 4.18.0-12-generic on a Lenovo Thinkpad
Situation: While the notebook runs with kernel version 4.18.0-11-generic, I can start vmplayer, it compiles (if needed) its kernel module (vmmon.ko and vmnet.ko) and then starts the virtual machine without any problem.
After updating to kernel version 4.18.0-12-generic, vmplayer compiles again both modules, however the modules cannot be loaded anymore. Loading the modules manually leads to the following error message:
root@koehn-ThinkPad# modprobe -v vmmon
insmod /lib/modules/4.18.0-12-generic/misc/vmmon.ko
modprobe: ERROR: could not insert 'vmmon': Operation not permitted
If I reboot the system and start again 4.18.0-11-generic, everything is fine again.
Does anybody have an idea?
BTW, I also tried 4.18.0-13-generic. The result is identical to -12.
drivers kernel vmware 18.10
drivers kernel vmware 18.10
asked Jan 12 at 17:00
MartinMartin
31
New contributor
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 12 at 17:00
MartinMartin
31
New contributor
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 12 at 17:00
MartinMartin
31
New contributor
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 12 at 17:00
MartinMartin
31
asked Jan 12 at 17:00
MartinMartin
31
31
New contributor
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Martin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It sounds like you have UEFI Secure Boot enabled.
There are two main choices:
- disable Secure Boot
- enable your kernel models to be signed for secure boot
Option 1 is simpler-- you'll want to go into you BIOS menu and disable secure boot. How this is done varies by computer, but typically you'll need to press F2 or DEL at the first startup screen. Once in there, you'll need to look for the "secure boot" option and turn it off.
Option 2 means that you need to generate a certificate and then teach your computer to trust it. That's covered by this page: https://wiki.ubuntu.com/UEFI/SecureBoot
answered Jan 12 at 20:44
Aaron BentleyAaron Bentley
1162
New contributor
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thanks for this hint. You're totally right. To check it quickly, I used option 1, now it is working again. The only thing what I really don't understand: what has changed between the two patch level -11 and -12 which prohibits starting of unsigned kernel modules? I see no hint in the ubuntu kernel change log...
– Martin
Jan 12 at 21:35
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
});
}
});
Martin is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1109169%2fvmplayer-doesnt-load-modules-anymore%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
It sounds like you have UEFI Secure Boot enabled.
There are two main choices:
- disable Secure Boot
- enable your kernel models to be signed for secure boot
Option 1 is simpler-- you'll want to go into you BIOS menu and disable secure boot. How this is done varies by computer, but typically you'll need to press F2 or DEL at the first startup screen. Once in there, you'll need to look for the "secure boot" option and turn it off.
Option 2 means that you need to generate a certificate and then teach your computer to trust it. That's covered by this page: https://wiki.ubuntu.com/UEFI/SecureBoot
answered Jan 12 at 20:44
Aaron BentleyAaron Bentley
1162
New contributor
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thanks for this hint. You're totally right. To check it quickly, I used option 1, now it is working again. The only thing what I really don't understand: what has changed between the two patch level -11 and -12 which prohibits starting of unsigned kernel modules? I see no hint in the ubuntu kernel change log...
– Martin
Jan 12 at 21:35
add a comment |
It sounds like you have UEFI Secure Boot enabled.
There are two main choices:
- disable Secure Boot
- enable your kernel models to be signed for secure boot
Option 1 is simpler-- you'll want to go into you BIOS menu and disable secure boot. How this is done varies by computer, but typically you'll need to press F2 or DEL at the first startup screen. Once in there, you'll need to look for the "secure boot" option and turn it off.
Option 2 means that you need to generate a certificate and then teach your computer to trust it. That's covered by this page: https://wiki.ubuntu.com/UEFI/SecureBoot
answered Jan 12 at 20:44
Aaron BentleyAaron Bentley
1162
New contributor
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thanks for this hint. You're totally right. To check it quickly, I used option 1, now it is working again. The only thing what I really don't understand: what has changed between the two patch level -11 and -12 which prohibits starting of unsigned kernel modules? I see no hint in the ubuntu kernel change log...
– Martin
Jan 12 at 21:35
add a comment |
It sounds like you have UEFI Secure Boot enabled.
There are two main choices:
- disable Secure Boot
- enable your kernel models to be signed for secure boot
Option 1 is simpler-- you'll want to go into you BIOS menu and disable secure boot. How this is done varies by computer, but typically you'll need to press F2 or DEL at the first startup screen. Once in there, you'll need to look for the "secure boot" option and turn it off.
Option 2 means that you need to generate a certificate and then teach your computer to trust it. That's covered by this page: https://wiki.ubuntu.com/UEFI/SecureBoot
answered Jan 12 at 20:44
Aaron BentleyAaron Bentley
1162
New contributor
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
It sounds like you have UEFI Secure Boot enabled.
There are two main choices:
- disable Secure Boot
- enable your kernel models to be signed for secure boot
Option 1 is simpler-- you'll want to go into you BIOS menu and disable secure boot. How this is done varies by computer, but typically you'll need to press F2 or DEL at the first startup screen. Once in there, you'll need to look for the "secure boot" option and turn it off.
Option 2 means that you need to generate a certificate and then teach your computer to trust it. That's covered by this page: https://wiki.ubuntu.com/UEFI/SecureBoot
answered Jan 12 at 20:44
Aaron BentleyAaron Bentley
1162
New contributor
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Jan 12 at 20:44
Aaron BentleyAaron Bentley
1162
New contributor
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Jan 12 at 20:44
Aaron BentleyAaron Bentley
1162
answered Jan 12 at 20:44
Aaron BentleyAaron Bentley
1162
1162
New contributor
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Aaron Bentley is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thanks for this hint. You're totally right. To check it quickly, I used option 1, now it is working again. The only thing what I really don't understand: what has changed between the two patch level -11 and -12 which prohibits starting of unsigned kernel modules? I see no hint in the ubuntu kernel change log...
– Martin
Jan 12 at 21:35
add a comment |
Thanks for this hint. You're totally right. To check it quickly, I used option 1, now it is working again. The only thing what I really don't understand: what has changed between the two patch level -11 and -12 which prohibits starting of unsigned kernel modules? I see no hint in the ubuntu kernel change log...
– Martin
Jan 12 at 21:35
Thanks for this hint. You're totally right. To check it quickly, I used option 1, now it is working again. The only thing what I really don't understand: what has changed between the two patch level -11 and -12 which prohibits starting of unsigned kernel modules? I see no hint in the ubuntu kernel change log...
– Martin
Jan 12 at 21:35
Thanks for this hint. You're totally right. To check it quickly, I used option 1, now it is working again. The only thing what I really don't understand: what has changed between the two patch level -11 and -12 which prohibits starting of unsigned kernel modules? I see no hint in the ubuntu kernel change log...
– Martin
Jan 12 at 21:35
add a comment |
Martin is a new contributor. Be nice, and check out our Code of Conduct.
Martin is a new contributor. Be nice, and check out our Code of Conduct.
Martin is a new contributor. Be nice, and check out our Code of Conduct.
Martin is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1109169%2fvmplayer-doesnt-load-modules-anymore%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
