Ubuntu 18.04.1 hangs at “Booting SMP configuration” on VMware
I found some related questions, e.g. Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?, but my case a is a big different:
I am running VMware Workstation 14.1.3 on a server with Intel(R) Xeon(R) CPUs E5-1650.
I had a VM with Ubuntu 14.04 with four cores, which I upgraded to Ubuntu 18.04.
The kernel is 4.15.0-36-generic.
Since the upgrade, the VM won't boot anymore, it gets stuck at "Booting SMP configuration".
If I change the VM to have one core only, it boots successfully.
Also, I can boot by choosing a 4.4.0 kernel during the boot process.
I cannot apply any of the Virtualbox-specific options, has anybody else experienced this with VMware and knows how to fix it?
Update:
I had a look at the vmware.log for the VM, and the last entries are these:
2018-10-09T13:43:12.054+02:00| vcpu-0| W115: CPU microcode update available.
2018-10-09T13:43:12.054+02:00| vcpu-0| W115+ The guest OS tried to update the microcode from patch level 60 (3Ch) to patch level 61 (3Dh), but VMware Workstation does not allow microcode patches to be applied from within a virtual machine.
2018-10-09T13:43:12.054+02:00| vcpu-0| W115+ Microcode patches are used to correct CPU errata. You may be able to obtain a BIOS/firmware update which includes this microcode patch from your system vendor, or your host OS may provide a facility for loading microcode patches.CPU reset: soft (mode 0
However, these are only warnings, so I suppose it does not play a role.
boot 18.04 vmware
asked Oct 8 '18 at 13:27
abulholabulhol
62
add a comment |
I found some related questions, e.g. Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?, but my case a is a big different:
I am running VMware Workstation 14.1.3 on a server with Intel(R) Xeon(R) CPUs E5-1650.
I had a VM with Ubuntu 14.04 with four cores, which I upgraded to Ubuntu 18.04.
The kernel is 4.15.0-36-generic.
Since the upgrade, the VM won't boot anymore, it gets stuck at "Booting SMP configuration".
If I change the VM to have one core only, it boots successfully.
Also, I can boot by choosing a 4.4.0 kernel during the boot process.
I cannot apply any of the Virtualbox-specific options, has anybody else experienced this with VMware and knows how to fix it?
Update:
I had a look at the vmware.log for the VM, and the last entries are these:
2018-10-09T13:43:12.054+02:00| vcpu-0| W115: CPU microcode update available.
2018-10-09T13:43:12.054+02:00| vcpu-0| W115+ The guest OS tried to update the microcode from patch level 60 (3Ch) to patch level 61 (3Dh), but VMware Workstation does not allow microcode patches to be applied from within a virtual machine.
2018-10-09T13:43:12.054+02:00| vcpu-0| W115+ Microcode patches are used to correct CPU errata. You may be able to obtain a BIOS/firmware update which includes this microcode patch from your system vendor, or your host OS may provide a facility for loading microcode patches.CPU reset: soft (mode 0
However, these are only warnings, so I suppose it does not play a role.
boot 18.04 vmware
asked Oct 8 '18 at 13:27
abulholabulhol
62
add a comment |
I found some related questions, e.g. Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?, but my case a is a big different:
I am running VMware Workstation 14.1.3 on a server with Intel(R) Xeon(R) CPUs E5-1650.
I had a VM with Ubuntu 14.04 with four cores, which I upgraded to Ubuntu 18.04.
The kernel is 4.15.0-36-generic.
Since the upgrade, the VM won't boot anymore, it gets stuck at "Booting SMP configuration".
If I change the VM to have one core only, it boots successfully.
Also, I can boot by choosing a 4.4.0 kernel during the boot process.
I cannot apply any of the Virtualbox-specific options, has anybody else experienced this with VMware and knows how to fix it?
Update:
I had a look at the vmware.log for the VM, and the last entries are these:
2018-10-09T13:43:12.054+02:00| vcpu-0| W115: CPU microcode update available.
2018-10-09T13:43:12.054+02:00| vcpu-0| W115+ The guest OS tried to update the microcode from patch level 60 (3Ch) to patch level 61 (3Dh), but VMware Workstation does not allow microcode patches to be applied from within a virtual machine.
2018-10-09T13:43:12.054+02:00| vcpu-0| W115+ Microcode patches are used to correct CPU errata. You may be able to obtain a BIOS/firmware update which includes this microcode patch from your system vendor, or your host OS may provide a facility for loading microcode patches.CPU reset: soft (mode 0
However, these are only warnings, so I suppose it does not play a role.
boot 18.04 vmware
asked Oct 8 '18 at 13:27
abulholabulhol
62
I found some related questions, e.g. Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?, but my case a is a big different:
I am running VMware Workstation 14.1.3 on a server with Intel(R) Xeon(R) CPUs E5-1650.
I had a VM with Ubuntu 14.04 with four cores, which I upgraded to Ubuntu 18.04.
The kernel is 4.15.0-36-generic.
Since the upgrade, the VM won't boot anymore, it gets stuck at "Booting SMP configuration".
If I change the VM to have one core only, it boots successfully.
Also, I can boot by choosing a 4.4.0 kernel during the boot process.
I cannot apply any of the Virtualbox-specific options, has anybody else experienced this with VMware and knows how to fix it?
Update:
I had a look at the vmware.log for the VM, and the last entries are these:
2018-10-09T13:43:12.054+02:00| vcpu-0| W115: CPU microcode update available.
2018-10-09T13:43:12.054+02:00| vcpu-0| W115+ The guest OS tried to update the microcode from patch level 60 (3Ch) to patch level 61 (3Dh), but VMware Workstation does not allow microcode patches to be applied from within a virtual machine.
2018-10-09T13:43:12.054+02:00| vcpu-0| W115+ Microcode patches are used to correct CPU errata. You may be able to obtain a BIOS/firmware update which includes this microcode patch from your system vendor, or your host OS may provide a facility for loading microcode patches.CPU reset: soft (mode 0
However, these are only warnings, so I suppose it does not play a role.
boot 18.04 vmware
boot 18.04 vmware
asked Oct 8 '18 at 13:27
abulholabulhol
62
asked Oct 8 '18 at 13:27
abulholabulhol
62
edited Oct 9 '18 at 11:56
abulhol
asked Oct 8 '18 at 13:27
abulholabulhol
62
asked Oct 8 '18 at 13:27
abulholabulhol
62
asked Oct 8 '18 at 13:27
abulholabulhol
62
62
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I bumped against this as well for several days. Had an idea based off of reading the esxi logs about failing to apply an intel mcirocode update and decided to see if it was possible to remove it and sure enough that fixed it.
Post I got the idea from: https://ubuntuforums.org/showthread.php?t=2273643
Had to boot into reovery mode to execute the following commands: https://wiki.ubuntu.com/RecoveryMode
Commands I ran to get it working.
sudo dpkg -l|grep intel
sudo apt-get purge intel-microcode
sudo update-grub
sudo reboot
answered Dec 29 '18 at 1:53
Jeremiah PhilippJeremiah Philipp
11
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%2f1081973%2fubuntu-18-04-1-hangs-at-booting-smp-configuration-on-vmware%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
I bumped against this as well for several days. Had an idea based off of reading the esxi logs about failing to apply an intel mcirocode update and decided to see if it was possible to remove it and sure enough that fixed it.
Post I got the idea from: https://ubuntuforums.org/showthread.php?t=2273643
Had to boot into reovery mode to execute the following commands: https://wiki.ubuntu.com/RecoveryMode
Commands I ran to get it working.
sudo dpkg -l|grep intel
sudo apt-get purge intel-microcode
sudo update-grub
sudo reboot
answered Dec 29 '18 at 1:53
Jeremiah PhilippJeremiah Philipp
11
add a comment |
I bumped against this as well for several days. Had an idea based off of reading the esxi logs about failing to apply an intel mcirocode update and decided to see if it was possible to remove it and sure enough that fixed it.
Post I got the idea from: https://ubuntuforums.org/showthread.php?t=2273643
Had to boot into reovery mode to execute the following commands: https://wiki.ubuntu.com/RecoveryMode
Commands I ran to get it working.
sudo dpkg -l|grep intel
sudo apt-get purge intel-microcode
sudo update-grub
sudo reboot
answered Dec 29 '18 at 1:53
Jeremiah PhilippJeremiah Philipp
11
add a comment |
I bumped against this as well for several days. Had an idea based off of reading the esxi logs about failing to apply an intel mcirocode update and decided to see if it was possible to remove it and sure enough that fixed it.
Post I got the idea from: https://ubuntuforums.org/showthread.php?t=2273643
Had to boot into reovery mode to execute the following commands: https://wiki.ubuntu.com/RecoveryMode
Commands I ran to get it working.
sudo dpkg -l|grep intel
sudo apt-get purge intel-microcode
sudo update-grub
sudo reboot
answered Dec 29 '18 at 1:53
Jeremiah PhilippJeremiah Philipp
11
I bumped against this as well for several days. Had an idea based off of reading the esxi logs about failing to apply an intel mcirocode update and decided to see if it was possible to remove it and sure enough that fixed it.
Post I got the idea from: https://ubuntuforums.org/showthread.php?t=2273643
Had to boot into reovery mode to execute the following commands: https://wiki.ubuntu.com/RecoveryMode
Commands I ran to get it working.
sudo dpkg -l|grep intel
sudo apt-get purge intel-microcode
sudo update-grub
sudo reboot
answered Dec 29 '18 at 1:53
Jeremiah PhilippJeremiah Philipp
11
edited Dec 29 '18 at 2:35
answered Dec 29 '18 at 1:53
Jeremiah PhilippJeremiah Philipp
11
answered Dec 29 '18 at 1:53
Jeremiah PhilippJeremiah Philipp
11
answered Dec 29 '18 at 1:53
Jeremiah PhilippJeremiah Philipp
11
11
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%2f1081973%2fubuntu-18-04-1-hangs-at-booting-smp-configuration-on-vmware%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
