How to troubleshoot booting to a black screen on virtualbox
I was using 13.04 as a guest OS on my Virtualbox 14.2.18. Host is Windows 8.
After upgrade to 13.10 ubuntu does not start. I can see black screen and blinking cursor.
Can anyone help? I am pretty new to ubuntu. My feeling is that it is somethign wrong with graphic drivers. I can access tty and all files (/home) are there.
virtualbox windows-8
edited Jun 19 '17 at 11:01
muru
1
asked Nov 5 '13 at 11:16
dondon
123115
add a comment |
I was using 13.04 as a guest OS on my Virtualbox 14.2.18. Host is Windows 8.
After upgrade to 13.10 ubuntu does not start. I can see black screen and blinking cursor.
Can anyone help? I am pretty new to ubuntu. My feeling is that it is somethign wrong with graphic drivers. I can access tty and all files (/home) are there.
virtualbox windows-8
edited Jun 19 '17 at 11:01
muru
1
asked Nov 5 '13 at 11:16
dondon
123115
add a comment |
I was using 13.04 as a guest OS on my Virtualbox 14.2.18. Host is Windows 8.
After upgrade to 13.10 ubuntu does not start. I can see black screen and blinking cursor.
Can anyone help? I am pretty new to ubuntu. My feeling is that it is somethign wrong with graphic drivers. I can access tty and all files (/home) are there.
virtualbox windows-8
edited Jun 19 '17 at 11:01
muru
1
asked Nov 5 '13 at 11:16
dondon
123115
I was using 13.04 as a guest OS on my Virtualbox 14.2.18. Host is Windows 8.
After upgrade to 13.10 ubuntu does not start. I can see black screen and blinking cursor.
Can anyone help? I am pretty new to ubuntu. My feeling is that it is somethign wrong with graphic drivers. I can access tty and all files (/home) are there.
virtualbox windows-8
virtualbox windows-8
edited Jun 19 '17 at 11:01
muru
1
asked Nov 5 '13 at 11:16
dondon
123115
edited Jun 19 '17 at 11:01
muru
1
asked Nov 5 '13 at 11:16
dondon
123115
edited Jun 19 '17 at 11:01
muru
1
edited Jun 19 '17 at 11:01
muru
1
edited Jun 19 '17 at 11:01
muru
1
1
asked Nov 5 '13 at 11:16
dondon
123115
asked Nov 5 '13 at 11:16
dondon
123115
asked Nov 5 '13 at 11:16
dondon
123115
123115
add a comment |
add a comment |
15 Answers
15
active
oldest
votes
This is how I troubleshoot a non-starting Ubuntu in Virtual Box (assuming optimal settings for a virtual machine were already made):
- Make sure you had installed the most recent version of Virtual Box.
Try a reboot by entering a TTY terminal (Host + F1)
sudo reboot
Update the guest OS from TTY (Host + F1):
sudo apt update && sudo apt dist-upgrade
Install guest additions from command line.
- Reboot the guest after installing the guest additions.
Start lightdm manually from a TTY (Host + F1) with
sudo lightdm
Try several reboots of the VM. Due to timing issues it may help eventually.
- Try a reboot of the host.
- Check forums and virtualbox.org for known bugs.
answered Nov 5 '13 at 11:55
TakkatTakkat
107k35249376
I've updated VIrtualBox to 4.3.2 and installed additions. Now I see login page from ubuntu. After typing password it shows black screen with popup: "System program problem detected. Do you want to report a problem now?" after pressing Report problem 4 times nothing happens. Black screen is there.
– don
Nov 5 '13 at 15:31
This message is seen on bare metal too - its bugs which may hopefully be fixed sooner or later. Until then your VM may still need occasional reboots, or manual starts of lightdm from TTY. Not much we can do.
– Takkat
Nov 5 '13 at 15:37
is there any way to downgrade or migrate my data from this installation to another?
– don
Nov 5 '13 at 15:56
Downgrade is not recommended. But you could copy & paste your HOME to restore it elsewhere. However I am pretty confident it will be much more stable soon.
– Takkat
Nov 5 '13 at 18:43
1
Already solved my issue by Step 2 - thank you!
– Nick Coad
Jun 20 '16 at 8:49
add a comment |
I had this problem and my solution was simple.
Somehow, my VirtualBox configuration for the VM (Ubuntu) was changed after a Virtual Box upgrade. My guest VM was Ubuntu 64 bits and it was configured as 32 bits version. To change:
- Open Virtual Box
- Select your virtual machine and click in
"Configurations" - Go to "General"
- Change the version to "Ubuntu (64-bit)"
answered Nov 1 '15 at 23:50
DherikDherik
33327
1
Why negative? This is really resolve my problem.
– Dherik
Mar 11 '16 at 15:17
2
Happened to me after transferring machine files to another machine and re-installing virtual box. This fixed my problem.
– Orestis P.
Jun 10 '16 at 5:42
1
Worked for me too!
– Erik Berkun-Drevnig
Jul 9 '16 at 23:20
1
For me too! Thx!
– Antonio Petricca
Nov 28 '16 at 16:23
1
This really was the right hint for me, to go to the bios and enable Virtualisation. Kudos
– Abderrahmane TAHRI JOUTI
Mar 16 '17 at 9:38
|
show 3 more comments
For me, none of the above answers worked. I solved this problem by disabling 3d acceleration on the vm settings page. This is quite odd since I've been using 3D acceleration flawlessly for months on that VM.
answered Jun 19 '17 at 11:01
pomarcpomarc
19112
add a comment |
This maybe an answer:
You (and me) get to this screen through an (accidental) host+f9. It doesn't tell you what happened though.
The reverse magic spell is alt+f7 (everything restored in its former glory).
I had to discover this myself. Though getting into trouble was easy enough.
answered Jun 2 '14 at 16:37
user287749user287749
5112
add a comment |
This happens to me today after upgrade VBox to 5.1.30.
The logon screen looks normal. After login in, however, the screen becomes black and remain black, while VBox manager preview showing the desktop.
Tried various suggestions, the only thing that works is to disable 3D acceleration for guest OS (Linux Mint18).
Guest addition update has no effect.
answered Oct 21 '17 at 18:52
user750199user750199
411
add a comment |
When I got to the login screen, I turned fullscreen mode off, logged in, then turned it back on. It worked. I might have just been lucky, though.
answered Mar 17 '14 at 14:32
aomimezuraaomimezura
311
add a comment |
I had the same issue installing Kali in VirtualBox, blinking cursors on the upper left corner. The simple solution for me was entering BIOS by pressing F10 during boot, and enabling virtualization.
edited Sep 23 '16 at 3:24
SuperSluether
7271721
answered Sep 22 '16 at 23:02
WilliamRWilliamR
311
add a comment |
I did the following as it worked for me.
Open TTYL (Ctrl + Alt + F1)
Login to a regular user account (not guest).
Enter
sudo dpkg --configure -aPress (Ctrl + F7)
edited Nov 30 '16 at 18:40
Mark Yisri
832624
answered Nov 30 '16 at 16:23
AnkitAnkit
311
This worked for me.
– Viraj
Oct 2 '18 at 5:50
add a comment |
Here is how I resolved the issue. I had installed Hadoop on my guest openSuse OS. There are several services which needs to be started to start working on Hadoop like,
start-dfs.sh
start-yarn.sh
I added both the above start command in my .bashrc file so that I don't have to start them explicitly everytime I login. .bashrc gets executed every time login.
$cd ~
$vi .bashrc
I commented my start service commands as shown below.
answered Apr 7 '17 at 14:00
Vinayak DornalaVinayak Dornala
1312
add a comment |
I had a similar problem, what I did was:
- Enter into Setting --> System --> Processor
- Set Processor to 2CPU instead of 1CPU
- Click OK and restart.
Worked fine for me after
answered Jul 9 '18 at 1:40
V.NoviceV.Novice
211
add a comment |
The following works for my Ubuntu 16.04 inside VirtualBox:
- Shutdown Ubuntu guest OS
- Go to Settings -> System -> Motherboard
- Change Chipset from ICH9 to PIIX3
- Restart Ubuntu and the graphics mode becomes normal
Strangely, ICH9 works fine until one day when I upgraded VirtualBox from 5.0.18 to 5.1.28.
edited Sep 21 '17 at 17:17
Owen Hines
2,42511034
answered Sep 21 '17 at 8:34
Joe X ZhuJoe X Zhu
1
add a comment |
Nothing worked, so I booted into recovery mode and selected the DPKG option (repair broken packages) and after that did it.
answered Nov 20 '17 at 13:06
VindolinVindolin
1032
Are you saying that you had broken packages?
– user535733
Nov 20 '17 at 16:10
add a comment |
I had the same issue with Linux Mint on VirtualBox 5.2.22.
I could see the boot screen but after boot it would go to a black screen and remain black.
My Base Memory was set at 512 MB. I bumped it to 1024 MB and it got past boot and into the desktop.
answered Jan 5 at 21:34
narmageddonnarmageddon
1
add a comment |
When trying to boot Ubuntu on in virtual box I had a black screen until I went into
settings > system and unchecked "enable EFI".
Ubuntu booted up successfully after I did that.
answered Jan 8 at 14:02
StephenStephen
1
add a comment |
I had a frozen black screen of the graphical interface. An Ubuntu 18.04 VM running on VirtualBox 6.0, on Windows 8 host. Changing the Display -> Graphics Controller to VMSVGA fixed it.
answered Jan 29 at 21:55
drgnfrdrgnfr
1
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%2f371432%2fhow-to-troubleshoot-booting-to-a-black-screen-on-virtualbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
15 Answers
15
active
oldest
votes
15 Answers
15
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is how I troubleshoot a non-starting Ubuntu in Virtual Box (assuming optimal settings for a virtual machine were already made):
- Make sure you had installed the most recent version of Virtual Box.
Try a reboot by entering a TTY terminal (Host + F1)
sudo reboot
Update the guest OS from TTY (Host + F1):
sudo apt update && sudo apt dist-upgrade
Install guest additions from command line.
- Reboot the guest after installing the guest additions.
Start lightdm manually from a TTY (Host + F1) with
sudo lightdm
Try several reboots of the VM. Due to timing issues it may help eventually.
- Try a reboot of the host.
- Check forums and virtualbox.org for known bugs.
answered Nov 5 '13 at 11:55
TakkatTakkat
107k35249376
I've updated VIrtualBox to 4.3.2 and installed additions. Now I see login page from ubuntu. After typing password it shows black screen with popup: "System program problem detected. Do you want to report a problem now?" after pressing Report problem 4 times nothing happens. Black screen is there.
– don
Nov 5 '13 at 15:31
This message is seen on bare metal too - its bugs which may hopefully be fixed sooner or later. Until then your VM may still need occasional reboots, or manual starts of lightdm from TTY. Not much we can do.
– Takkat
Nov 5 '13 at 15:37
is there any way to downgrade or migrate my data from this installation to another?
– don
Nov 5 '13 at 15:56
Downgrade is not recommended. But you could copy & paste your HOME to restore it elsewhere. However I am pretty confident it will be much more stable soon.
– Takkat
Nov 5 '13 at 18:43
1
Already solved my issue by Step 2 - thank you!
– Nick Coad
Jun 20 '16 at 8:49
add a comment |
This is how I troubleshoot a non-starting Ubuntu in Virtual Box (assuming optimal settings for a virtual machine were already made):
- Make sure you had installed the most recent version of Virtual Box.
Try a reboot by entering a TTY terminal (Host + F1)
sudo reboot
Update the guest OS from TTY (Host + F1):
sudo apt update && sudo apt dist-upgrade
Install guest additions from command line.
- Reboot the guest after installing the guest additions.
Start lightdm manually from a TTY (Host + F1) with
sudo lightdm
Try several reboots of the VM. Due to timing issues it may help eventually.
- Try a reboot of the host.
- Check forums and virtualbox.org for known bugs.
answered Nov 5 '13 at 11:55
TakkatTakkat
107k35249376
I've updated VIrtualBox to 4.3.2 and installed additions. Now I see login page from ubuntu. After typing password it shows black screen with popup: "System program problem detected. Do you want to report a problem now?" after pressing Report problem 4 times nothing happens. Black screen is there.
– don
Nov 5 '13 at 15:31
This message is seen on bare metal too - its bugs which may hopefully be fixed sooner or later. Until then your VM may still need occasional reboots, or manual starts of lightdm from TTY. Not much we can do.
– Takkat
Nov 5 '13 at 15:37
is there any way to downgrade or migrate my data from this installation to another?
– don
Nov 5 '13 at 15:56
Downgrade is not recommended. But you could copy & paste your HOME to restore it elsewhere. However I am pretty confident it will be much more stable soon.
– Takkat
Nov 5 '13 at 18:43
1
Already solved my issue by Step 2 - thank you!
– Nick Coad
Jun 20 '16 at 8:49
add a comment |
This is how I troubleshoot a non-starting Ubuntu in Virtual Box (assuming optimal settings for a virtual machine were already made):
- Make sure you had installed the most recent version of Virtual Box.
Try a reboot by entering a TTY terminal (Host + F1)
sudo reboot
Update the guest OS from TTY (Host + F1):
sudo apt update && sudo apt dist-upgrade
Install guest additions from command line.
- Reboot the guest after installing the guest additions.
Start lightdm manually from a TTY (Host + F1) with
sudo lightdm
Try several reboots of the VM. Due to timing issues it may help eventually.
- Try a reboot of the host.
- Check forums and virtualbox.org for known bugs.
answered Nov 5 '13 at 11:55
TakkatTakkat
107k35249376
This is how I troubleshoot a non-starting Ubuntu in Virtual Box (assuming optimal settings for a virtual machine were already made):
- Make sure you had installed the most recent version of Virtual Box.
Try a reboot by entering a TTY terminal (Host + F1)
sudo reboot
Update the guest OS from TTY (Host + F1):
sudo apt update && sudo apt dist-upgrade
Install guest additions from command line.
- Reboot the guest after installing the guest additions.
Start lightdm manually from a TTY (Host + F1) with
sudo lightdm
Try several reboots of the VM. Due to timing issues it may help eventually.
- Try a reboot of the host.
- Check forums and virtualbox.org for known bugs.
answered Nov 5 '13 at 11:55
TakkatTakkat
107k35249376
edited Sep 10 '18 at 9:31
answered Nov 5 '13 at 11:55
TakkatTakkat
107k35249376
answered Nov 5 '13 at 11:55
TakkatTakkat
107k35249376
answered Nov 5 '13 at 11:55
TakkatTakkat
107k35249376
107k35249376
I've updated VIrtualBox to 4.3.2 and installed additions. Now I see login page from ubuntu. After typing password it shows black screen with popup: "System program problem detected. Do you want to report a problem now?" after pressing Report problem 4 times nothing happens. Black screen is there.
– don
Nov 5 '13 at 15:31
This message is seen on bare metal too - its bugs which may hopefully be fixed sooner or later. Until then your VM may still need occasional reboots, or manual starts of lightdm from TTY. Not much we can do.
– Takkat
Nov 5 '13 at 15:37
is there any way to downgrade or migrate my data from this installation to another?
– don
Nov 5 '13 at 15:56
Downgrade is not recommended. But you could copy & paste your HOME to restore it elsewhere. However I am pretty confident it will be much more stable soon.
– Takkat
Nov 5 '13 at 18:43
1
Already solved my issue by Step 2 - thank you!
– Nick Coad
Jun 20 '16 at 8:49
add a comment |
I've updated VIrtualBox to 4.3.2 and installed additions. Now I see login page from ubuntu. After typing password it shows black screen with popup: "System program problem detected. Do you want to report a problem now?" after pressing Report problem 4 times nothing happens. Black screen is there.
– don
Nov 5 '13 at 15:31
This message is seen on bare metal too - its bugs which may hopefully be fixed sooner or later. Until then your VM may still need occasional reboots, or manual starts of lightdm from TTY. Not much we can do.
– Takkat
Nov 5 '13 at 15:37
is there any way to downgrade or migrate my data from this installation to another?
– don
Nov 5 '13 at 15:56
Downgrade is not recommended. But you could copy & paste your HOME to restore it elsewhere. However I am pretty confident it will be much more stable soon.
– Takkat
Nov 5 '13 at 18:43
1
Already solved my issue by Step 2 - thank you!
– Nick Coad
Jun 20 '16 at 8:49
I've updated VIrtualBox to 4.3.2 and installed additions. Now I see login page from ubuntu. After typing password it shows black screen with popup: "System program problem detected. Do you want to report a problem now?" after pressing Report problem 4 times nothing happens. Black screen is there.
– don
Nov 5 '13 at 15:31
I've updated VIrtualBox to 4.3.2 and installed additions. Now I see login page from ubuntu. After typing password it shows black screen with popup: "System program problem detected. Do you want to report a problem now?" after pressing Report problem 4 times nothing happens. Black screen is there.
– don
Nov 5 '13 at 15:31
This message is seen on bare metal too - its bugs which may hopefully be fixed sooner or later. Until then your VM may still need occasional reboots, or manual starts of lightdm from TTY. Not much we can do.
– Takkat
Nov 5 '13 at 15:37
This message is seen on bare metal too - its bugs which may hopefully be fixed sooner or later. Until then your VM may still need occasional reboots, or manual starts of lightdm from TTY. Not much we can do.
– Takkat
Nov 5 '13 at 15:37
is there any way to downgrade or migrate my data from this installation to another?
– don
Nov 5 '13 at 15:56
is there any way to downgrade or migrate my data from this installation to another?
– don
Nov 5 '13 at 15:56
Downgrade is not recommended. But you could copy & paste your HOME to restore it elsewhere. However I am pretty confident it will be much more stable soon.
– Takkat
Nov 5 '13 at 18:43
Downgrade is not recommended. But you could copy & paste your HOME to restore it elsewhere. However I am pretty confident it will be much more stable soon.
– Takkat
Nov 5 '13 at 18:43
1
1
Already solved my issue by Step 2 - thank you!
– Nick Coad
Jun 20 '16 at 8:49
Already solved my issue by Step 2 - thank you!
– Nick Coad
Jun 20 '16 at 8:49
add a comment |
I had this problem and my solution was simple.
Somehow, my VirtualBox configuration for the VM (Ubuntu) was changed after a Virtual Box upgrade. My guest VM was Ubuntu 64 bits and it was configured as 32 bits version. To change:
- Open Virtual Box
- Select your virtual machine and click in
"Configurations" - Go to "General"
- Change the version to "Ubuntu (64-bit)"
answered Nov 1 '15 at 23:50
DherikDherik
33327
1
Why negative? This is really resolve my problem.
– Dherik
Mar 11 '16 at 15:17
2
Happened to me after transferring machine files to another machine and re-installing virtual box. This fixed my problem.
– Orestis P.
Jun 10 '16 at 5:42
1
Worked for me too!
– Erik Berkun-Drevnig
Jul 9 '16 at 23:20
1
For me too! Thx!
– Antonio Petricca
Nov 28 '16 at 16:23
1
This really was the right hint for me, to go to the bios and enable Virtualisation. Kudos
– Abderrahmane TAHRI JOUTI
Mar 16 '17 at 9:38
|
show 3 more comments
I had this problem and my solution was simple.
Somehow, my VirtualBox configuration for the VM (Ubuntu) was changed after a Virtual Box upgrade. My guest VM was Ubuntu 64 bits and it was configured as 32 bits version. To change:
- Open Virtual Box
- Select your virtual machine and click in
"Configurations" - Go to "General"
- Change the version to "Ubuntu (64-bit)"
answered Nov 1 '15 at 23:50
DherikDherik
33327
1
Why negative? This is really resolve my problem.
– Dherik
Mar 11 '16 at 15:17
2
Happened to me after transferring machine files to another machine and re-installing virtual box. This fixed my problem.
– Orestis P.
Jun 10 '16 at 5:42
1
Worked for me too!
– Erik Berkun-Drevnig
Jul 9 '16 at 23:20
1
For me too! Thx!
– Antonio Petricca
Nov 28 '16 at 16:23
1
This really was the right hint for me, to go to the bios and enable Virtualisation. Kudos
– Abderrahmane TAHRI JOUTI
Mar 16 '17 at 9:38
|
show 3 more comments
I had this problem and my solution was simple.
Somehow, my VirtualBox configuration for the VM (Ubuntu) was changed after a Virtual Box upgrade. My guest VM was Ubuntu 64 bits and it was configured as 32 bits version. To change:
- Open Virtual Box
- Select your virtual machine and click in
"Configurations" - Go to "General"
- Change the version to "Ubuntu (64-bit)"
answered Nov 1 '15 at 23:50
DherikDherik
33327
I had this problem and my solution was simple.
Somehow, my VirtualBox configuration for the VM (Ubuntu) was changed after a Virtual Box upgrade. My guest VM was Ubuntu 64 bits and it was configured as 32 bits version. To change:
- Open Virtual Box
- Select your virtual machine and click in
"Configurations" - Go to "General"
- Change the version to "Ubuntu (64-bit)"
answered Nov 1 '15 at 23:50
DherikDherik
33327
answered Nov 1 '15 at 23:50
DherikDherik
33327
answered Nov 1 '15 at 23:50
DherikDherik
33327
answered Nov 1 '15 at 23:50
DherikDherik
33327
33327
1
Why negative? This is really resolve my problem.
– Dherik
Mar 11 '16 at 15:17
2
Happened to me after transferring machine files to another machine and re-installing virtual box. This fixed my problem.
– Orestis P.
Jun 10 '16 at 5:42
1
Worked for me too!
– Erik Berkun-Drevnig
Jul 9 '16 at 23:20
1
For me too! Thx!
– Antonio Petricca
Nov 28 '16 at 16:23
1
This really was the right hint for me, to go to the bios and enable Virtualisation. Kudos
– Abderrahmane TAHRI JOUTI
Mar 16 '17 at 9:38
|
show 3 more comments
1
Why negative? This is really resolve my problem.
– Dherik
Mar 11 '16 at 15:17
2
Happened to me after transferring machine files to another machine and re-installing virtual box. This fixed my problem.
– Orestis P.
Jun 10 '16 at 5:42
1
Worked for me too!
– Erik Berkun-Drevnig
Jul 9 '16 at 23:20
1
For me too! Thx!
– Antonio Petricca
Nov 28 '16 at 16:23
1
This really was the right hint for me, to go to the bios and enable Virtualisation. Kudos
– Abderrahmane TAHRI JOUTI
Mar 16 '17 at 9:38
1
1
Why negative? This is really resolve my problem.
– Dherik
Mar 11 '16 at 15:17
Why negative? This is really resolve my problem.
– Dherik
Mar 11 '16 at 15:17
2
2
Happened to me after transferring machine files to another machine and re-installing virtual box. This fixed my problem.
– Orestis P.
Jun 10 '16 at 5:42
Happened to me after transferring machine files to another machine and re-installing virtual box. This fixed my problem.
– Orestis P.
Jun 10 '16 at 5:42
1
1
Worked for me too!
– Erik Berkun-Drevnig
Jul 9 '16 at 23:20
Worked for me too!
– Erik Berkun-Drevnig
Jul 9 '16 at 23:20
1
1
For me too! Thx!
– Antonio Petricca
Nov 28 '16 at 16:23
For me too! Thx!
– Antonio Petricca
Nov 28 '16 at 16:23
1
1
This really was the right hint for me, to go to the bios and enable Virtualisation. Kudos
– Abderrahmane TAHRI JOUTI
Mar 16 '17 at 9:38
This really was the right hint for me, to go to the bios and enable Virtualisation. Kudos
– Abderrahmane TAHRI JOUTI
Mar 16 '17 at 9:38
|
show 3 more comments
For me, none of the above answers worked. I solved this problem by disabling 3d acceleration on the vm settings page. This is quite odd since I've been using 3D acceleration flawlessly for months on that VM.
answered Jun 19 '17 at 11:01
pomarcpomarc
19112
add a comment |
For me, none of the above answers worked. I solved this problem by disabling 3d acceleration on the vm settings page. This is quite odd since I've been using 3D acceleration flawlessly for months on that VM.
answered Jun 19 '17 at 11:01
pomarcpomarc
19112
add a comment |
For me, none of the above answers worked. I solved this problem by disabling 3d acceleration on the vm settings page. This is quite odd since I've been using 3D acceleration flawlessly for months on that VM.
answered Jun 19 '17 at 11:01
pomarcpomarc
19112
For me, none of the above answers worked. I solved this problem by disabling 3d acceleration on the vm settings page. This is quite odd since I've been using 3D acceleration flawlessly for months on that VM.
answered Jun 19 '17 at 11:01
pomarcpomarc
19112
answered Jun 19 '17 at 11:01
pomarcpomarc
19112
answered Jun 19 '17 at 11:01
pomarcpomarc
19112
answered Jun 19 '17 at 11:01
pomarcpomarc
19112
19112
add a comment |
add a comment |
This maybe an answer:
You (and me) get to this screen through an (accidental) host+f9. It doesn't tell you what happened though.
The reverse magic spell is alt+f7 (everything restored in its former glory).
I had to discover this myself. Though getting into trouble was easy enough.
answered Jun 2 '14 at 16:37
user287749user287749
5112
add a comment |
This maybe an answer:
You (and me) get to this screen through an (accidental) host+f9. It doesn't tell you what happened though.
The reverse magic spell is alt+f7 (everything restored in its former glory).
I had to discover this myself. Though getting into trouble was easy enough.
answered Jun 2 '14 at 16:37
user287749user287749
5112
add a comment |
This maybe an answer:
You (and me) get to this screen through an (accidental) host+f9. It doesn't tell you what happened though.
The reverse magic spell is alt+f7 (everything restored in its former glory).
I had to discover this myself. Though getting into trouble was easy enough.
answered Jun 2 '14 at 16:37
user287749user287749
5112
This maybe an answer:
You (and me) get to this screen through an (accidental) host+f9. It doesn't tell you what happened though.
The reverse magic spell is alt+f7 (everything restored in its former glory).
I had to discover this myself. Though getting into trouble was easy enough.
answered Jun 2 '14 at 16:37
user287749user287749
5112
edited Sep 12 '17 at 20:44
answered Jun 2 '14 at 16:37
user287749user287749
5112
answered Jun 2 '14 at 16:37
user287749user287749
5112
answered Jun 2 '14 at 16:37
user287749user287749
5112
5112
add a comment |
add a comment |
This happens to me today after upgrade VBox to 5.1.30.
The logon screen looks normal. After login in, however, the screen becomes black and remain black, while VBox manager preview showing the desktop.
Tried various suggestions, the only thing that works is to disable 3D acceleration for guest OS (Linux Mint18).
Guest addition update has no effect.
answered Oct 21 '17 at 18:52
user750199user750199
411
add a comment |
This happens to me today after upgrade VBox to 5.1.30.
The logon screen looks normal. After login in, however, the screen becomes black and remain black, while VBox manager preview showing the desktop.
Tried various suggestions, the only thing that works is to disable 3D acceleration for guest OS (Linux Mint18).
Guest addition update has no effect.
answered Oct 21 '17 at 18:52
user750199user750199
411
add a comment |
This happens to me today after upgrade VBox to 5.1.30.
The logon screen looks normal. After login in, however, the screen becomes black and remain black, while VBox manager preview showing the desktop.
Tried various suggestions, the only thing that works is to disable 3D acceleration for guest OS (Linux Mint18).
Guest addition update has no effect.
answered Oct 21 '17 at 18:52
user750199user750199
411
This happens to me today after upgrade VBox to 5.1.30.
The logon screen looks normal. After login in, however, the screen becomes black and remain black, while VBox manager preview showing the desktop.
Tried various suggestions, the only thing that works is to disable 3D acceleration for guest OS (Linux Mint18).
Guest addition update has no effect.
answered Oct 21 '17 at 18:52
user750199user750199
411
answered Oct 21 '17 at 18:52
user750199user750199
411
answered Oct 21 '17 at 18:52
user750199user750199
411
answered Oct 21 '17 at 18:52
user750199user750199
411
411
add a comment |
add a comment |
When I got to the login screen, I turned fullscreen mode off, logged in, then turned it back on. It worked. I might have just been lucky, though.
answered Mar 17 '14 at 14:32
aomimezuraaomimezura
311
add a comment |
When I got to the login screen, I turned fullscreen mode off, logged in, then turned it back on. It worked. I might have just been lucky, though.
answered Mar 17 '14 at 14:32
aomimezuraaomimezura
311
add a comment |
When I got to the login screen, I turned fullscreen mode off, logged in, then turned it back on. It worked. I might have just been lucky, though.
answered Mar 17 '14 at 14:32
aomimezuraaomimezura
311
When I got to the login screen, I turned fullscreen mode off, logged in, then turned it back on. It worked. I might have just been lucky, though.
answered Mar 17 '14 at 14:32
aomimezuraaomimezura
311
answered Mar 17 '14 at 14:32
aomimezuraaomimezura
311
answered Mar 17 '14 at 14:32
aomimezuraaomimezura
311
answered Mar 17 '14 at 14:32
aomimezuraaomimezura
311
311
add a comment |
add a comment |
I had the same issue installing Kali in VirtualBox, blinking cursors on the upper left corner. The simple solution for me was entering BIOS by pressing F10 during boot, and enabling virtualization.
edited Sep 23 '16 at 3:24
SuperSluether
7271721
answered Sep 22 '16 at 23:02
WilliamRWilliamR
311
add a comment |
I had the same issue installing Kali in VirtualBox, blinking cursors on the upper left corner. The simple solution for me was entering BIOS by pressing F10 during boot, and enabling virtualization.
edited Sep 23 '16 at 3:24
SuperSluether
7271721
answered Sep 22 '16 at 23:02
WilliamRWilliamR
311
add a comment |
I had the same issue installing Kali in VirtualBox, blinking cursors on the upper left corner. The simple solution for me was entering BIOS by pressing F10 during boot, and enabling virtualization.
edited Sep 23 '16 at 3:24
SuperSluether
7271721
answered Sep 22 '16 at 23:02
WilliamRWilliamR
311
I had the same issue installing Kali in VirtualBox, blinking cursors on the upper left corner. The simple solution for me was entering BIOS by pressing F10 during boot, and enabling virtualization.
edited Sep 23 '16 at 3:24
SuperSluether
7271721
answered Sep 22 '16 at 23:02
WilliamRWilliamR
311
edited Sep 23 '16 at 3:24
SuperSluether
7271721
edited Sep 23 '16 at 3:24
SuperSluether
7271721
edited Sep 23 '16 at 3:24
SuperSluether
7271721
7271721
answered Sep 22 '16 at 23:02
WilliamRWilliamR
311
answered Sep 22 '16 at 23:02
WilliamRWilliamR
311
answered Sep 22 '16 at 23:02
WilliamRWilliamR
311
311
add a comment |
add a comment |
I did the following as it worked for me.
Open TTYL (Ctrl + Alt + F1)
Login to a regular user account (not guest).
Enter
sudo dpkg --configure -aPress (Ctrl + F7)
edited Nov 30 '16 at 18:40
Mark Yisri
832624
answered Nov 30 '16 at 16:23
AnkitAnkit
311
This worked for me.
– Viraj
Oct 2 '18 at 5:50
add a comment |
I did the following as it worked for me.
Open TTYL (Ctrl + Alt + F1)
Login to a regular user account (not guest).
Enter
sudo dpkg --configure -aPress (Ctrl + F7)
edited Nov 30 '16 at 18:40
Mark Yisri
832624
answered Nov 30 '16 at 16:23
AnkitAnkit
311
This worked for me.
– Viraj
Oct 2 '18 at 5:50
add a comment |
I did the following as it worked for me.
Open TTYL (Ctrl + Alt + F1)
Login to a regular user account (not guest).
Enter
sudo dpkg --configure -aPress (Ctrl + F7)
edited Nov 30 '16 at 18:40
Mark Yisri
832624
answered Nov 30 '16 at 16:23
AnkitAnkit
311
I did the following as it worked for me.
Open TTYL (Ctrl + Alt + F1)
Login to a regular user account (not guest).
Enter
sudo dpkg --configure -aPress (Ctrl + F7)
edited Nov 30 '16 at 18:40
Mark Yisri
832624
answered Nov 30 '16 at 16:23
AnkitAnkit
311
edited Nov 30 '16 at 18:40
Mark Yisri
832624
edited Nov 30 '16 at 18:40
Mark Yisri
832624
edited Nov 30 '16 at 18:40
Mark Yisri
832624
832624
answered Nov 30 '16 at 16:23
AnkitAnkit
311
answered Nov 30 '16 at 16:23
AnkitAnkit
311
answered Nov 30 '16 at 16:23
AnkitAnkit
311
311
This worked for me.
– Viraj
Oct 2 '18 at 5:50
add a comment |
This worked for me.
– Viraj
Oct 2 '18 at 5:50
This worked for me.
– Viraj
Oct 2 '18 at 5:50
This worked for me.
– Viraj
Oct 2 '18 at 5:50
add a comment |
Here is how I resolved the issue. I had installed Hadoop on my guest openSuse OS. There are several services which needs to be started to start working on Hadoop like,
start-dfs.sh
start-yarn.sh
I added both the above start command in my .bashrc file so that I don't have to start them explicitly everytime I login. .bashrc gets executed every time login.
$cd ~
$vi .bashrc
I commented my start service commands as shown below.
answered Apr 7 '17 at 14:00
Vinayak DornalaVinayak Dornala
1312
add a comment |
Here is how I resolved the issue. I had installed Hadoop on my guest openSuse OS. There are several services which needs to be started to start working on Hadoop like,
start-dfs.sh
start-yarn.sh
I added both the above start command in my .bashrc file so that I don't have to start them explicitly everytime I login. .bashrc gets executed every time login.
$cd ~
$vi .bashrc
I commented my start service commands as shown below.
answered Apr 7 '17 at 14:00
Vinayak DornalaVinayak Dornala
1312
add a comment |
Here is how I resolved the issue. I had installed Hadoop on my guest openSuse OS. There are several services which needs to be started to start working on Hadoop like,
start-dfs.sh
start-yarn.sh
I added both the above start command in my .bashrc file so that I don't have to start them explicitly everytime I login. .bashrc gets executed every time login.
$cd ~
$vi .bashrc
I commented my start service commands as shown below.
answered Apr 7 '17 at 14:00
Vinayak DornalaVinayak Dornala
1312
Here is how I resolved the issue. I had installed Hadoop on my guest openSuse OS. There are several services which needs to be started to start working on Hadoop like,
start-dfs.sh
start-yarn.sh
I added both the above start command in my .bashrc file so that I don't have to start them explicitly everytime I login. .bashrc gets executed every time login.
$cd ~
$vi .bashrc
I commented my start service commands as shown below.
answered Apr 7 '17 at 14:00
Vinayak DornalaVinayak Dornala
1312
answered Apr 7 '17 at 14:00
Vinayak DornalaVinayak Dornala
1312
answered Apr 7 '17 at 14:00
Vinayak DornalaVinayak Dornala
1312
answered Apr 7 '17 at 14:00
Vinayak DornalaVinayak Dornala
1312
1312
add a comment |
add a comment |
I had a similar problem, what I did was:
- Enter into Setting --> System --> Processor
- Set Processor to 2CPU instead of 1CPU
- Click OK and restart.
Worked fine for me after
answered Jul 9 '18 at 1:40
V.NoviceV.Novice
211
add a comment |
I had a similar problem, what I did was:
- Enter into Setting --> System --> Processor
- Set Processor to 2CPU instead of 1CPU
- Click OK and restart.
Worked fine for me after
answered Jul 9 '18 at 1:40
V.NoviceV.Novice
211
add a comment |
I had a similar problem, what I did was:
- Enter into Setting --> System --> Processor
- Set Processor to 2CPU instead of 1CPU
- Click OK and restart.
Worked fine for me after
answered Jul 9 '18 at 1:40
V.NoviceV.Novice
211
I had a similar problem, what I did was:
- Enter into Setting --> System --> Processor
- Set Processor to 2CPU instead of 1CPU
- Click OK and restart.
Worked fine for me after
answered Jul 9 '18 at 1:40
V.NoviceV.Novice
211
answered Jul 9 '18 at 1:40
V.NoviceV.Novice
211
answered Jul 9 '18 at 1:40
V.NoviceV.Novice
211
answered Jul 9 '18 at 1:40
V.NoviceV.Novice
211
211
add a comment |
add a comment |
The following works for my Ubuntu 16.04 inside VirtualBox:
- Shutdown Ubuntu guest OS
- Go to Settings -> System -> Motherboard
- Change Chipset from ICH9 to PIIX3
- Restart Ubuntu and the graphics mode becomes normal
Strangely, ICH9 works fine until one day when I upgraded VirtualBox from 5.0.18 to 5.1.28.
edited Sep 21 '17 at 17:17
Owen Hines
2,42511034
answered Sep 21 '17 at 8:34
Joe X ZhuJoe X Zhu
1
add a comment |
The following works for my Ubuntu 16.04 inside VirtualBox:
- Shutdown Ubuntu guest OS
- Go to Settings -> System -> Motherboard
- Change Chipset from ICH9 to PIIX3
- Restart Ubuntu and the graphics mode becomes normal
Strangely, ICH9 works fine until one day when I upgraded VirtualBox from 5.0.18 to 5.1.28.
edited Sep 21 '17 at 17:17
Owen Hines
2,42511034
answered Sep 21 '17 at 8:34
Joe X ZhuJoe X Zhu
1
add a comment |
The following works for my Ubuntu 16.04 inside VirtualBox:
- Shutdown Ubuntu guest OS
- Go to Settings -> System -> Motherboard
- Change Chipset from ICH9 to PIIX3
- Restart Ubuntu and the graphics mode becomes normal
Strangely, ICH9 works fine until one day when I upgraded VirtualBox from 5.0.18 to 5.1.28.
edited Sep 21 '17 at 17:17
Owen Hines
2,42511034
answered Sep 21 '17 at 8:34
Joe X ZhuJoe X Zhu
1
The following works for my Ubuntu 16.04 inside VirtualBox:
- Shutdown Ubuntu guest OS
- Go to Settings -> System -> Motherboard
- Change Chipset from ICH9 to PIIX3
- Restart Ubuntu and the graphics mode becomes normal
Strangely, ICH9 works fine until one day when I upgraded VirtualBox from 5.0.18 to 5.1.28.
edited Sep 21 '17 at 17:17
Owen Hines
2,42511034
answered Sep 21 '17 at 8:34
Joe X ZhuJoe X Zhu
1
edited Sep 21 '17 at 17:17
Owen Hines
2,42511034
edited Sep 21 '17 at 17:17
Owen Hines
2,42511034
edited Sep 21 '17 at 17:17
Owen Hines
2,42511034
2,42511034
answered Sep 21 '17 at 8:34
Joe X ZhuJoe X Zhu
1
answered Sep 21 '17 at 8:34
Joe X ZhuJoe X Zhu
1
answered Sep 21 '17 at 8:34
Joe X ZhuJoe X Zhu
1
1
add a comment |
add a comment |
Nothing worked, so I booted into recovery mode and selected the DPKG option (repair broken packages) and after that did it.
answered Nov 20 '17 at 13:06
VindolinVindolin
1032
Are you saying that you had broken packages?
– user535733
Nov 20 '17 at 16:10
add a comment |
Nothing worked, so I booted into recovery mode and selected the DPKG option (repair broken packages) and after that did it.
answered Nov 20 '17 at 13:06
VindolinVindolin
1032
Are you saying that you had broken packages?
– user535733
Nov 20 '17 at 16:10
add a comment |
Nothing worked, so I booted into recovery mode and selected the DPKG option (repair broken packages) and after that did it.
answered Nov 20 '17 at 13:06
VindolinVindolin
1032
Nothing worked, so I booted into recovery mode and selected the DPKG option (repair broken packages) and after that did it.
answered Nov 20 '17 at 13:06
VindolinVindolin
1032
answered Nov 20 '17 at 13:06
VindolinVindolin
1032
answered Nov 20 '17 at 13:06
VindolinVindolin
1032
answered Nov 20 '17 at 13:06
VindolinVindolin
1032
1032
Are you saying that you had broken packages?
– user535733
Nov 20 '17 at 16:10
add a comment |
Are you saying that you had broken packages?
– user535733
Nov 20 '17 at 16:10
Are you saying that you had broken packages?
– user535733
Nov 20 '17 at 16:10
Are you saying that you had broken packages?
– user535733
Nov 20 '17 at 16:10
add a comment |
I had the same issue with Linux Mint on VirtualBox 5.2.22.
I could see the boot screen but after boot it would go to a black screen and remain black.
My Base Memory was set at 512 MB. I bumped it to 1024 MB and it got past boot and into the desktop.
answered Jan 5 at 21:34
narmageddonnarmageddon
1
add a comment |
I had the same issue with Linux Mint on VirtualBox 5.2.22.
I could see the boot screen but after boot it would go to a black screen and remain black.
My Base Memory was set at 512 MB. I bumped it to 1024 MB and it got past boot and into the desktop.
answered Jan 5 at 21:34
narmageddonnarmageddon
1
add a comment |
I had the same issue with Linux Mint on VirtualBox 5.2.22.
I could see the boot screen but after boot it would go to a black screen and remain black.
My Base Memory was set at 512 MB. I bumped it to 1024 MB and it got past boot and into the desktop.
answered Jan 5 at 21:34
narmageddonnarmageddon
1
I had the same issue with Linux Mint on VirtualBox 5.2.22.
I could see the boot screen but after boot it would go to a black screen and remain black.
My Base Memory was set at 512 MB. I bumped it to 1024 MB and it got past boot and into the desktop.
answered Jan 5 at 21:34
narmageddonnarmageddon
1
answered Jan 5 at 21:34
narmageddonnarmageddon
1
answered Jan 5 at 21:34
narmageddonnarmageddon
1
answered Jan 5 at 21:34
narmageddonnarmageddon
1
1
add a comment |
add a comment |
When trying to boot Ubuntu on in virtual box I had a black screen until I went into
settings > system and unchecked "enable EFI".
Ubuntu booted up successfully after I did that.
answered Jan 8 at 14:02
StephenStephen
1
add a comment |
When trying to boot Ubuntu on in virtual box I had a black screen until I went into
settings > system and unchecked "enable EFI".
Ubuntu booted up successfully after I did that.
answered Jan 8 at 14:02
StephenStephen
1
add a comment |
When trying to boot Ubuntu on in virtual box I had a black screen until I went into
settings > system and unchecked "enable EFI".
Ubuntu booted up successfully after I did that.
answered Jan 8 at 14:02
StephenStephen
1
When trying to boot Ubuntu on in virtual box I had a black screen until I went into
settings > system and unchecked "enable EFI".
Ubuntu booted up successfully after I did that.
answered Jan 8 at 14:02
StephenStephen
1
answered Jan 8 at 14:02
StephenStephen
1
answered Jan 8 at 14:02
StephenStephen
1
answered Jan 8 at 14:02
StephenStephen
1
1
add a comment |
add a comment |
I had a frozen black screen of the graphical interface. An Ubuntu 18.04 VM running on VirtualBox 6.0, on Windows 8 host. Changing the Display -> Graphics Controller to VMSVGA fixed it.
answered Jan 29 at 21:55
drgnfrdrgnfr
1
add a comment |
I had a frozen black screen of the graphical interface. An Ubuntu 18.04 VM running on VirtualBox 6.0, on Windows 8 host. Changing the Display -> Graphics Controller to VMSVGA fixed it.
answered Jan 29 at 21:55
drgnfrdrgnfr
1
add a comment |
I had a frozen black screen of the graphical interface. An Ubuntu 18.04 VM running on VirtualBox 6.0, on Windows 8 host. Changing the Display -> Graphics Controller to VMSVGA fixed it.
answered Jan 29 at 21:55
drgnfrdrgnfr
1
I had a frozen black screen of the graphical interface. An Ubuntu 18.04 VM running on VirtualBox 6.0, on Windows 8 host. Changing the Display -> Graphics Controller to VMSVGA fixed it.
answered Jan 29 at 21:55
drgnfrdrgnfr
1
answered Jan 29 at 21:55
drgnfrdrgnfr
1
answered Jan 29 at 21:55
drgnfrdrgnfr
1
answered Jan 29 at 21:55
drgnfrdrgnfr
1
1
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%2f371432%2fhow-to-troubleshoot-booting-to-a-black-screen-on-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
