Upgrade to Linux kernel 4.15.0-44 in Ubuntu 18.04 breaks VirtualBox
A recent upgrade to the Linux 4.15.0-44 kernel broke VirtualBox on my system. I'm running Ubuntu 18.0.4. Haven't had time to investigate, but rebooting to 4.15.0-43 allowed virtual system to be booted.
Just wondering if anybody else has had this issue?
virtualbox
edited Jan 30 at 2:59
CentaurusA
2,2251424
asked Jan 30 at 2:00
RomanRoman
61
add a comment |
A recent upgrade to the Linux 4.15.0-44 kernel broke VirtualBox on my system. I'm running Ubuntu 18.0.4. Haven't had time to investigate, but rebooting to 4.15.0-43 allowed virtual system to be booted.
Just wondering if anybody else has had this issue?
virtualbox
edited Jan 30 at 2:59
CentaurusA
2,2251424
asked Jan 30 at 2:00
RomanRoman
61
I didn't try with VirtualBox, but the upgrade broke my multi-monitor setup (I have two external monitors, connecting them just froze the whole system). Something seems to be wrong with that version...
– rindPHI
Jan 30 at 8:11
What Virtualbox version are you using and how did you install it? I am using 5.2.26 on two systems and I have installed it from the official Oracle repo. Both copies work as they should after this kernel update on both the host and the guest systems. In general, it's better to use the Virtualbox versions offered by Oracle rather than the one in the Ubuntu repos.
– Stormlord
Jan 31 at 9:45
add a comment |
A recent upgrade to the Linux 4.15.0-44 kernel broke VirtualBox on my system. I'm running Ubuntu 18.0.4. Haven't had time to investigate, but rebooting to 4.15.0-43 allowed virtual system to be booted.
Just wondering if anybody else has had this issue?
virtualbox
edited Jan 30 at 2:59
CentaurusA
2,2251424
asked Jan 30 at 2:00
RomanRoman
61
A recent upgrade to the Linux 4.15.0-44 kernel broke VirtualBox on my system. I'm running Ubuntu 18.0.4. Haven't had time to investigate, but rebooting to 4.15.0-43 allowed virtual system to be booted.
Just wondering if anybody else has had this issue?
virtualbox
virtualbox
edited Jan 30 at 2:59
CentaurusA
2,2251424
asked Jan 30 at 2:00
RomanRoman
61
edited Jan 30 at 2:59
CentaurusA
2,2251424
asked Jan 30 at 2:00
RomanRoman
61
edited Jan 30 at 2:59
CentaurusA
2,2251424
edited Jan 30 at 2:59
CentaurusA
2,2251424
edited Jan 30 at 2:59
CentaurusA
2,2251424
2,2251424
asked Jan 30 at 2:00
RomanRoman
61
asked Jan 30 at 2:00
RomanRoman
61
asked Jan 30 at 2:00
RomanRoman
61
61
I didn't try with VirtualBox, but the upgrade broke my multi-monitor setup (I have two external monitors, connecting them just froze the whole system). Something seems to be wrong with that version...
– rindPHI
Jan 30 at 8:11
What Virtualbox version are you using and how did you install it? I am using 5.2.26 on two systems and I have installed it from the official Oracle repo. Both copies work as they should after this kernel update on both the host and the guest systems. In general, it's better to use the Virtualbox versions offered by Oracle rather than the one in the Ubuntu repos.
– Stormlord
Jan 31 at 9:45
add a comment |
I didn't try with VirtualBox, but the upgrade broke my multi-monitor setup (I have two external monitors, connecting them just froze the whole system). Something seems to be wrong with that version...
– rindPHI
Jan 30 at 8:11
What Virtualbox version are you using and how did you install it? I am using 5.2.26 on two systems and I have installed it from the official Oracle repo. Both copies work as they should after this kernel update on both the host and the guest systems. In general, it's better to use the Virtualbox versions offered by Oracle rather than the one in the Ubuntu repos.
– Stormlord
Jan 31 at 9:45
I didn't try with VirtualBox, but the upgrade broke my multi-monitor setup (I have two external monitors, connecting them just froze the whole system). Something seems to be wrong with that version...
– rindPHI
Jan 30 at 8:11
I didn't try with VirtualBox, but the upgrade broke my multi-monitor setup (I have two external monitors, connecting them just froze the whole system). Something seems to be wrong with that version...
– rindPHI
Jan 30 at 8:11
What Virtualbox version are you using and how did you install it? I am using 5.2.26 on two systems and I have installed it from the official Oracle repo. Both copies work as they should after this kernel update on both the host and the guest systems. In general, it's better to use the Virtualbox versions offered by Oracle rather than the one in the Ubuntu repos.
– Stormlord
Jan 31 at 9:45
What Virtualbox version are you using and how did you install it? I am using 5.2.26 on two systems and I have installed it from the official Oracle repo. Both copies work as they should after this kernel update on both the host and the guest systems. In general, it's better to use the Virtualbox versions offered by Oracle rather than the one in the Ubuntu repos.
– Stormlord
Jan 31 at 9:45
add a comment |
3 Answers
3
active
oldest
votes
Canonical seems to have recognized this issue and released another version already. They probably just reverted it back to 4.15.0-43 but called it 4.15.0-45 just to make a quick fix, so we'll probably see another kernel version soon after they resolve 4.15.0-44's issues.
answered Jan 31 at 17:06
Samuel GarciaSamuel Garcia
212
add a comment |
Not directly related to your problem, but this update pretty much broke everything for me as I'm not able to boot / or booting into black screen (not sure if nvidia driver was at fault but it did not get updated - only the kernel).
This is due to an issue with the kernel not being able to detect USB devices (I have an external USB drive attached), but even after disabling the disk it still won't boot.
After reverting to the previous kernel the problem(s) disappeared.
answered Jan 31 at 9:06
deemokdeemok
1112
add a comment |
On my laptop there were several negative effects, it was not trackable to dedicated actions. Examples:
- spurious USB oops messages
- login in gnome UI session leads to a black screen (no way out, no mouse, no Ctrl+Alt+Fx)
- shutdown does not drive the machine into the right power state (energy remains on)
...
This 4.15.0-44 was a pure nightmare...
edited Feb 11 at 17:26
mature
2,0871728
answered Jan 31 at 18:58
jdehaanjdehaan
1313
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%2f1113991%2fupgrade-to-linux-kernel-4-15-0-44-in-ubuntu-18-04-breaks-virtualbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Canonical seems to have recognized this issue and released another version already. They probably just reverted it back to 4.15.0-43 but called it 4.15.0-45 just to make a quick fix, so we'll probably see another kernel version soon after they resolve 4.15.0-44's issues.
answered Jan 31 at 17:06
Samuel GarciaSamuel Garcia
212
add a comment |
Canonical seems to have recognized this issue and released another version already. They probably just reverted it back to 4.15.0-43 but called it 4.15.0-45 just to make a quick fix, so we'll probably see another kernel version soon after they resolve 4.15.0-44's issues.
answered Jan 31 at 17:06
Samuel GarciaSamuel Garcia
212
add a comment |
Canonical seems to have recognized this issue and released another version already. They probably just reverted it back to 4.15.0-43 but called it 4.15.0-45 just to make a quick fix, so we'll probably see another kernel version soon after they resolve 4.15.0-44's issues.
answered Jan 31 at 17:06
Samuel GarciaSamuel Garcia
212
Canonical seems to have recognized this issue and released another version already. They probably just reverted it back to 4.15.0-43 but called it 4.15.0-45 just to make a quick fix, so we'll probably see another kernel version soon after they resolve 4.15.0-44's issues.
answered Jan 31 at 17:06
Samuel GarciaSamuel Garcia
212
answered Jan 31 at 17:06
Samuel GarciaSamuel Garcia
212
answered Jan 31 at 17:06
Samuel GarciaSamuel Garcia
212
answered Jan 31 at 17:06
Samuel GarciaSamuel Garcia
212
212
add a comment |
add a comment |
Not directly related to your problem, but this update pretty much broke everything for me as I'm not able to boot / or booting into black screen (not sure if nvidia driver was at fault but it did not get updated - only the kernel).
This is due to an issue with the kernel not being able to detect USB devices (I have an external USB drive attached), but even after disabling the disk it still won't boot.
After reverting to the previous kernel the problem(s) disappeared.
answered Jan 31 at 9:06
deemokdeemok
1112
add a comment |
Not directly related to your problem, but this update pretty much broke everything for me as I'm not able to boot / or booting into black screen (not sure if nvidia driver was at fault but it did not get updated - only the kernel).
This is due to an issue with the kernel not being able to detect USB devices (I have an external USB drive attached), but even after disabling the disk it still won't boot.
After reverting to the previous kernel the problem(s) disappeared.
answered Jan 31 at 9:06
deemokdeemok
1112
add a comment |
Not directly related to your problem, but this update pretty much broke everything for me as I'm not able to boot / or booting into black screen (not sure if nvidia driver was at fault but it did not get updated - only the kernel).
This is due to an issue with the kernel not being able to detect USB devices (I have an external USB drive attached), but even after disabling the disk it still won't boot.
After reverting to the previous kernel the problem(s) disappeared.
answered Jan 31 at 9:06
deemokdeemok
1112
Not directly related to your problem, but this update pretty much broke everything for me as I'm not able to boot / or booting into black screen (not sure if nvidia driver was at fault but it did not get updated - only the kernel).
This is due to an issue with the kernel not being able to detect USB devices (I have an external USB drive attached), but even after disabling the disk it still won't boot.
After reverting to the previous kernel the problem(s) disappeared.
answered Jan 31 at 9:06
deemokdeemok
1112
answered Jan 31 at 9:06
deemokdeemok
1112
answered Jan 31 at 9:06
deemokdeemok
1112
answered Jan 31 at 9:06
deemokdeemok
1112
1112
add a comment |
add a comment |
On my laptop there were several negative effects, it was not trackable to dedicated actions. Examples:
- spurious USB oops messages
- login in gnome UI session leads to a black screen (no way out, no mouse, no Ctrl+Alt+Fx)
- shutdown does not drive the machine into the right power state (energy remains on)
...
This 4.15.0-44 was a pure nightmare...
edited Feb 11 at 17:26
mature
2,0871728
answered Jan 31 at 18:58
jdehaanjdehaan
1313
add a comment |
On my laptop there were several negative effects, it was not trackable to dedicated actions. Examples:
- spurious USB oops messages
- login in gnome UI session leads to a black screen (no way out, no mouse, no Ctrl+Alt+Fx)
- shutdown does not drive the machine into the right power state (energy remains on)
...
This 4.15.0-44 was a pure nightmare...
edited Feb 11 at 17:26
mature
2,0871728
answered Jan 31 at 18:58
jdehaanjdehaan
1313
add a comment |
On my laptop there were several negative effects, it was not trackable to dedicated actions. Examples:
- spurious USB oops messages
- login in gnome UI session leads to a black screen (no way out, no mouse, no Ctrl+Alt+Fx)
- shutdown does not drive the machine into the right power state (energy remains on)
...
This 4.15.0-44 was a pure nightmare...
edited Feb 11 at 17:26
mature
2,0871728
answered Jan 31 at 18:58
jdehaanjdehaan
1313
On my laptop there were several negative effects, it was not trackable to dedicated actions. Examples:
- spurious USB oops messages
- login in gnome UI session leads to a black screen (no way out, no mouse, no Ctrl+Alt+Fx)
- shutdown does not drive the machine into the right power state (energy remains on)
...
This 4.15.0-44 was a pure nightmare...
edited Feb 11 at 17:26
mature
2,0871728
answered Jan 31 at 18:58
jdehaanjdehaan
1313
edited Feb 11 at 17:26
mature
2,0871728
edited Feb 11 at 17:26
mature
2,0871728
edited Feb 11 at 17:26
mature
2,0871728
2,0871728
answered Jan 31 at 18:58
jdehaanjdehaan
1313
answered Jan 31 at 18:58
jdehaanjdehaan
1313
answered Jan 31 at 18:58
jdehaanjdehaan
1313
1313
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%2f1113991%2fupgrade-to-linux-kernel-4-15-0-44-in-ubuntu-18-04-breaks-virtualbox%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
I didn't try with VirtualBox, but the upgrade broke my multi-monitor setup (I have two external monitors, connecting them just froze the whole system). Something seems to be wrong with that version...
– rindPHI
Jan 30 at 8:11
What Virtualbox version are you using and how did you install it? I am using 5.2.26 on two systems and I have installed it from the official Oracle repo. Both copies work as they should after this kernel update on both the host and the guest systems. In general, it's better to use the Virtualbox versions offered by Oracle rather than the one in the Ubuntu repos.
– Stormlord
Jan 31 at 9:45