Centos 7 Failed to start LSB: VirtualBox Linux Additions kernel modules
Clash Royale CLAN TAG#URR8PPP
Recently ran updates on one of my Centos 7 Development Environments (server) which is running though Parallels on Mac OSX, when I went to start the VM recently I received this output:
[FAILED] Failed to start LSB: VirtualBox Linux Additions kernel modules.
See 'systemctl status vboxadd.service' for details.
[FAILED] Failed to start LSB: VirtualBox Linux Additions service.
See 'systemctl status vboxadd-service.service' for details.
Centos 7 output
It does not boot, it freezes at the last shown output and never continues.
I've seen this issue before, it crept up on one of my other Virtual Machines, and after hours of research now in 2 separate events, I wanted to reach out to see if anyone knows how to go about solving this, I can't find documentation on it anywhere, and i'm not using Virtual Box I'm using Parallels.
How do I go about solving this?
Thanks!
centos virtualbox boot
migrated from serverfault.com Mar 17 '17 at 12:49
This question came from our site for system and network administrators.
add a comment |
Recently ran updates on one of my Centos 7 Development Environments (server) which is running though Parallels on Mac OSX, when I went to start the VM recently I received this output:
[FAILED] Failed to start LSB: VirtualBox Linux Additions kernel modules.
See 'systemctl status vboxadd.service' for details.
[FAILED] Failed to start LSB: VirtualBox Linux Additions service.
See 'systemctl status vboxadd-service.service' for details.
Centos 7 output
It does not boot, it freezes at the last shown output and never continues.
I've seen this issue before, it crept up on one of my other Virtual Machines, and after hours of research now in 2 separate events, I wanted to reach out to see if anyone knows how to go about solving this, I can't find documentation on it anywhere, and i'm not using Virtual Box I'm using Parallels.
How do I go about solving this?
Thanks!
centos virtualbox boot
migrated from serverfault.com Mar 17 '17 at 12:49
This question came from our site for system and network administrators.
add a comment |
Recently ran updates on one of my Centos 7 Development Environments (server) which is running though Parallels on Mac OSX, when I went to start the VM recently I received this output:
[FAILED] Failed to start LSB: VirtualBox Linux Additions kernel modules.
See 'systemctl status vboxadd.service' for details.
[FAILED] Failed to start LSB: VirtualBox Linux Additions service.
See 'systemctl status vboxadd-service.service' for details.
Centos 7 output
It does not boot, it freezes at the last shown output and never continues.
I've seen this issue before, it crept up on one of my other Virtual Machines, and after hours of research now in 2 separate events, I wanted to reach out to see if anyone knows how to go about solving this, I can't find documentation on it anywhere, and i'm not using Virtual Box I'm using Parallels.
How do I go about solving this?
Thanks!
centos virtualbox boot
Recently ran updates on one of my Centos 7 Development Environments (server) which is running though Parallels on Mac OSX, when I went to start the VM recently I received this output:
[FAILED] Failed to start LSB: VirtualBox Linux Additions kernel modules.
See 'systemctl status vboxadd.service' for details.
[FAILED] Failed to start LSB: VirtualBox Linux Additions service.
See 'systemctl status vboxadd-service.service' for details.
Centos 7 output
It does not boot, it freezes at the last shown output and never continues.
I've seen this issue before, it crept up on one of my other Virtual Machines, and after hours of research now in 2 separate events, I wanted to reach out to see if anyone knows how to go about solving this, I can't find documentation on it anywhere, and i'm not using Virtual Box I'm using Parallels.
How do I go about solving this?
Thanks!
centos virtualbox boot
centos virtualbox boot
asked Mar 17 '17 at 11:22
Wrekoniz3Wrekoniz3
11
11
migrated from serverfault.com Mar 17 '17 at 12:49
This question came from our site for system and network administrators.
migrated from serverfault.com Mar 17 '17 at 12:49
This question came from our site for system and network administrators.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
So, answered this one thanks to a friend.
When doing a kernel update, you have to update parallels tools apparently. The issue is, when updating the kernel the video drivers got crushed, VBox Addons seem like the are part of the Parallels tools suite, so the issue here was that it was hanging up because the system couldn't find a screen as a result of not having the correct video drivers.
Mounting the Parallels tools suite and updating, resolved the issue.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f352102%2fcentos-7-failed-to-start-lsb-virtualbox-linux-additions-kernel-modules%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
So, answered this one thanks to a friend.
When doing a kernel update, you have to update parallels tools apparently. The issue is, when updating the kernel the video drivers got crushed, VBox Addons seem like the are part of the Parallels tools suite, so the issue here was that it was hanging up because the system couldn't find a screen as a result of not having the correct video drivers.
Mounting the Parallels tools suite and updating, resolved the issue.
add a comment |
So, answered this one thanks to a friend.
When doing a kernel update, you have to update parallels tools apparently. The issue is, when updating the kernel the video drivers got crushed, VBox Addons seem like the are part of the Parallels tools suite, so the issue here was that it was hanging up because the system couldn't find a screen as a result of not having the correct video drivers.
Mounting the Parallels tools suite and updating, resolved the issue.
add a comment |
So, answered this one thanks to a friend.
When doing a kernel update, you have to update parallels tools apparently. The issue is, when updating the kernel the video drivers got crushed, VBox Addons seem like the are part of the Parallels tools suite, so the issue here was that it was hanging up because the system couldn't find a screen as a result of not having the correct video drivers.
Mounting the Parallels tools suite and updating, resolved the issue.
So, answered this one thanks to a friend.
When doing a kernel update, you have to update parallels tools apparently. The issue is, when updating the kernel the video drivers got crushed, VBox Addons seem like the are part of the Parallels tools suite, so the issue here was that it was hanging up because the system couldn't find a screen as a result of not having the correct video drivers.
Mounting the Parallels tools suite and updating, resolved the issue.
answered Mar 17 '17 at 19:16
Wrekoniz3Wrekoniz3
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f352102%2fcentos-7-failed-to-start-lsb-virtualbox-linux-additions-kernel-modules%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