Spectre Mitigation/lfence not serializing on VM Startup
I just a download Ubuntu 18.04.1 disk image to run off of Virtual Box, and whenever I start the VM it gives me the message "spectre v2 mitigation: lfence not serializing. switching to generic retpoline". After this it runs a trace and then stops. I'm not sure what to do about this. The other blog posts I saw where people had this issue were due to older GPU hardware (I'm running an Nvidia GTX 1060, so I wouldn't consider that too old) or because they were using an older version of Ubuntu. As far as I know, 18.04.1 is the latest version. Anyone know why this is happening?
boot virtualbox
add a comment |
I just a download Ubuntu 18.04.1 disk image to run off of Virtual Box, and whenever I start the VM it gives me the message "spectre v2 mitigation: lfence not serializing. switching to generic retpoline". After this it runs a trace and then stops. I'm not sure what to do about this. The other blog posts I saw where people had this issue were due to older GPU hardware (I'm running an Nvidia GTX 1060, so I wouldn't consider that too old) or because they were using an older version of Ubuntu. As far as I know, 18.04.1 is the latest version. Anyone know why this is happening?
boot virtualbox
add a comment |
I just a download Ubuntu 18.04.1 disk image to run off of Virtual Box, and whenever I start the VM it gives me the message "spectre v2 mitigation: lfence not serializing. switching to generic retpoline". After this it runs a trace and then stops. I'm not sure what to do about this. The other blog posts I saw where people had this issue were due to older GPU hardware (I'm running an Nvidia GTX 1060, so I wouldn't consider that too old) or because they were using an older version of Ubuntu. As far as I know, 18.04.1 is the latest version. Anyone know why this is happening?
boot virtualbox
I just a download Ubuntu 18.04.1 disk image to run off of Virtual Box, and whenever I start the VM it gives me the message "spectre v2 mitigation: lfence not serializing. switching to generic retpoline". After this it runs a trace and then stops. I'm not sure what to do about this. The other blog posts I saw where people had this issue were due to older GPU hardware (I'm running an Nvidia GTX 1060, so I wouldn't consider that too old) or because they were using an older version of Ubuntu. As far as I know, 18.04.1 is the latest version. Anyone know why this is happening?
boot virtualbox
boot virtualbox
asked Sep 14 '18 at 15:12
mxb1999mxb1999
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I am having the same problem with this version on Ubuntu in VirtualBox. I'm running on a new computer and I have SVM enabled in the bios.
Edit: Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?
This answer led me to try turning on an additional core in Settings -> System -> Processor which then would show the "Spectre v2..." text but still boot.
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%2f1075296%2fspectre-mitigation-lfence-not-serializing-on-vm-startup%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 am having the same problem with this version on Ubuntu in VirtualBox. I'm running on a new computer and I have SVM enabled in the bios.
Edit: Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?
This answer led me to try turning on an additional core in Settings -> System -> Processor which then would show the "Spectre v2..." text but still boot.
add a comment |
I am having the same problem with this version on Ubuntu in VirtualBox. I'm running on a new computer and I have SVM enabled in the bios.
Edit: Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?
This answer led me to try turning on an additional core in Settings -> System -> Processor which then would show the "Spectre v2..." text but still boot.
add a comment |
I am having the same problem with this version on Ubuntu in VirtualBox. I'm running on a new computer and I have SVM enabled in the bios.
Edit: Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?
This answer led me to try turning on an additional core in Settings -> System -> Processor which then would show the "Spectre v2..." text but still boot.
I am having the same problem with this version on Ubuntu in VirtualBox. I'm running on a new computer and I have SVM enabled in the bios.
Edit: Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?
This answer led me to try turning on an additional core in Settings -> System -> Processor which then would show the "Spectre v2..." text but still boot.
edited Sep 15 '18 at 20:14
answered Sep 15 '18 at 19:50
Windows 10 UserWindows 10 User
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%2f1075296%2fspectre-mitigation-lfence-not-serializing-on-vm-startup%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