Why is the Ubuntu VM screen corrupted on my HiDpi laptop?
When running a clean install of Ubuntu 17.04 on a fresh Dell XPS 9360 (3200x1800 display) I was soon shown the following screen after the initial boot:
Basically, the displayed image is corrupt and incomprehensible. What can I do to fix this?
ubuntu virtualbox dell-xps display-settings
asked May 8 '17 at 15:21
oligofrenoligofren
560927
add a comment |
When running a clean install of Ubuntu 17.04 on a fresh Dell XPS 9360 (3200x1800 display) I was soon shown the following screen after the initial boot:
Basically, the displayed image is corrupt and incomprehensible. What can I do to fix this?
ubuntu virtualbox dell-xps display-settings
asked May 8 '17 at 15:21
oligofrenoligofren
560927
add a comment |
When running a clean install of Ubuntu 17.04 on a fresh Dell XPS 9360 (3200x1800 display) I was soon shown the following screen after the initial boot:
Basically, the displayed image is corrupt and incomprehensible. What can I do to fix this?
ubuntu virtualbox dell-xps display-settings
asked May 8 '17 at 15:21
oligofrenoligofren
560927
When running a clean install of Ubuntu 17.04 on a fresh Dell XPS 9360 (3200x1800 display) I was soon shown the following screen after the initial boot:
Basically, the displayed image is corrupt and incomprehensible. What can I do to fix this?
ubuntu virtualbox dell-xps display-settings
ubuntu virtualbox dell-xps display-settings
asked May 8 '17 at 15:21
oligofrenoligofren
560927
asked May 8 '17 at 15:21
oligofrenoligofren
560927
asked May 8 '17 at 15:21
oligofrenoligofren
560927
asked May 8 '17 at 15:21
oligofrenoligofren
560927
asked May 8 '17 at 15:21
oligofrenoligofren
560927
560927
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
On my macOS host, increasing the amount of processors allocated to the VM from 1 -> 4 fixed this issue for me. My guest was Lubuntu 18.04.
answered Jun 17 '18 at 19:11
kaskas
844
2
It worked for me too.
– Jbm
Aug 25 '18 at 17:05
1
This was the only solution that worked for me, even though VirtualBox complains with "invalid settings detected" (since the host only has 2 CPUs).
– Reinier Torenbeek
Aug 27 '18 at 21:07
add a comment |
Basically, the allotted default amount of VRAM (video ram) in Virtualbox is not sufficient for the high-resolution display. Simply try increasing it. By increasing it from the default (19MB?) to 128MB the problem went away.
This might also be related to the Unity desktop environment, which according to the specs requires a video card of at least 256 MB, a requirement most integrated solutions will fail. In that case, try another desktop environment, such as XFCE (XUbuntu) which does not have a 3D rendered desktop by default.
answered May 8 '17 at 15:21
oligofrenoligofren
560927
I had mine at 64MB for Ubuntu Mate, which worked fine in 17.10, but needed 128MB for 18.04.
– Gringo Suave
Apr 6 '18 at 20:35
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1207163%2fwhy-is-the-ubuntu-vm-screen-corrupted-on-my-hidpi-laptop%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
On my macOS host, increasing the amount of processors allocated to the VM from 1 -> 4 fixed this issue for me. My guest was Lubuntu 18.04.
answered Jun 17 '18 at 19:11
kaskas
844
2
It worked for me too.
– Jbm
Aug 25 '18 at 17:05
1
This was the only solution that worked for me, even though VirtualBox complains with "invalid settings detected" (since the host only has 2 CPUs).
– Reinier Torenbeek
Aug 27 '18 at 21:07
add a comment |
On my macOS host, increasing the amount of processors allocated to the VM from 1 -> 4 fixed this issue for me. My guest was Lubuntu 18.04.
answered Jun 17 '18 at 19:11
kaskas
844
2
It worked for me too.
– Jbm
Aug 25 '18 at 17:05
1
This was the only solution that worked for me, even though VirtualBox complains with "invalid settings detected" (since the host only has 2 CPUs).
– Reinier Torenbeek
Aug 27 '18 at 21:07
add a comment |
On my macOS host, increasing the amount of processors allocated to the VM from 1 -> 4 fixed this issue for me. My guest was Lubuntu 18.04.
answered Jun 17 '18 at 19:11
kaskas
844
On my macOS host, increasing the amount of processors allocated to the VM from 1 -> 4 fixed this issue for me. My guest was Lubuntu 18.04.
answered Jun 17 '18 at 19:11
kaskas
844
edited Sep 8 '18 at 16:59
answered Jun 17 '18 at 19:11
kaskas
844
answered Jun 17 '18 at 19:11
kaskas
844
answered Jun 17 '18 at 19:11
kaskas
844
844
2
It worked for me too.
– Jbm
Aug 25 '18 at 17:05
1
This was the only solution that worked for me, even though VirtualBox complains with "invalid settings detected" (since the host only has 2 CPUs).
– Reinier Torenbeek
Aug 27 '18 at 21:07
add a comment |
2
It worked for me too.
– Jbm
Aug 25 '18 at 17:05
1
This was the only solution that worked for me, even though VirtualBox complains with "invalid settings detected" (since the host only has 2 CPUs).
– Reinier Torenbeek
Aug 27 '18 at 21:07
2
2
It worked for me too.
– Jbm
Aug 25 '18 at 17:05
It worked for me too.
– Jbm
Aug 25 '18 at 17:05
1
1
This was the only solution that worked for me, even though VirtualBox complains with "invalid settings detected" (since the host only has 2 CPUs).
– Reinier Torenbeek
Aug 27 '18 at 21:07
This was the only solution that worked for me, even though VirtualBox complains with "invalid settings detected" (since the host only has 2 CPUs).
– Reinier Torenbeek
Aug 27 '18 at 21:07
add a comment |
Basically, the allotted default amount of VRAM (video ram) in Virtualbox is not sufficient for the high-resolution display. Simply try increasing it. By increasing it from the default (19MB?) to 128MB the problem went away.
This might also be related to the Unity desktop environment, which according to the specs requires a video card of at least 256 MB, a requirement most integrated solutions will fail. In that case, try another desktop environment, such as XFCE (XUbuntu) which does not have a 3D rendered desktop by default.
answered May 8 '17 at 15:21
oligofrenoligofren
560927
I had mine at 64MB for Ubuntu Mate, which worked fine in 17.10, but needed 128MB for 18.04.
– Gringo Suave
Apr 6 '18 at 20:35
add a comment |
Basically, the allotted default amount of VRAM (video ram) in Virtualbox is not sufficient for the high-resolution display. Simply try increasing it. By increasing it from the default (19MB?) to 128MB the problem went away.
This might also be related to the Unity desktop environment, which according to the specs requires a video card of at least 256 MB, a requirement most integrated solutions will fail. In that case, try another desktop environment, such as XFCE (XUbuntu) which does not have a 3D rendered desktop by default.
answered May 8 '17 at 15:21
oligofrenoligofren
560927
I had mine at 64MB for Ubuntu Mate, which worked fine in 17.10, but needed 128MB for 18.04.
– Gringo Suave
Apr 6 '18 at 20:35
add a comment |
Basically, the allotted default amount of VRAM (video ram) in Virtualbox is not sufficient for the high-resolution display. Simply try increasing it. By increasing it from the default (19MB?) to 128MB the problem went away.
This might also be related to the Unity desktop environment, which according to the specs requires a video card of at least 256 MB, a requirement most integrated solutions will fail. In that case, try another desktop environment, such as XFCE (XUbuntu) which does not have a 3D rendered desktop by default.
answered May 8 '17 at 15:21
oligofrenoligofren
560927
Basically, the allotted default amount of VRAM (video ram) in Virtualbox is not sufficient for the high-resolution display. Simply try increasing it. By increasing it from the default (19MB?) to 128MB the problem went away.
This might also be related to the Unity desktop environment, which according to the specs requires a video card of at least 256 MB, a requirement most integrated solutions will fail. In that case, try another desktop environment, such as XFCE (XUbuntu) which does not have a 3D rendered desktop by default.
answered May 8 '17 at 15:21
oligofrenoligofren
560927
answered May 8 '17 at 15:21
oligofrenoligofren
560927
answered May 8 '17 at 15:21
oligofrenoligofren
560927
answered May 8 '17 at 15:21
oligofrenoligofren
560927
560927
I had mine at 64MB for Ubuntu Mate, which worked fine in 17.10, but needed 128MB for 18.04.
– Gringo Suave
Apr 6 '18 at 20:35
add a comment |
I had mine at 64MB for Ubuntu Mate, which worked fine in 17.10, but needed 128MB for 18.04.
– Gringo Suave
Apr 6 '18 at 20:35
I had mine at 64MB for Ubuntu Mate, which worked fine in 17.10, but needed 128MB for 18.04.
– Gringo Suave
Apr 6 '18 at 20:35
I had mine at 64MB for Ubuntu Mate, which worked fine in 17.10, but needed 128MB for 18.04.
– Gringo Suave
Apr 6 '18 at 20:35
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1207163%2fwhy-is-the-ubuntu-vm-screen-corrupted-on-my-hidpi-laptop%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
