Ubuntu 18.04 lts freezes while in boot, in wndows Virtual box. Solution?
Clash Royale CLAN TAG#URR8PPP up vote
6
down vote
favorite
I am Using Ubuntu in Virtual Box.. the Host OS is Windows10 with dedicated intel's Graphics.
I have reinstalled twice, probably this starts due to sudden shutdown or some reason. Dnt know whats the problem.
Saw a old post about this type on Ubuntu 12.04 / 14.04 LTS ... but their problem/ solution was on Nvidia Driver. And following that didnt help me!
.
Any solution ?
virtualbox windows freeze
asked Apr 30 at 15:26
Battleseeker_Rex
4116
add a comment |Â
up vote
6
down vote
favorite
I am Using Ubuntu in Virtual Box.. the Host OS is Windows10 with dedicated intel's Graphics.
I have reinstalled twice, probably this starts due to sudden shutdown or some reason. Dnt know whats the problem.
Saw a old post about this type on Ubuntu 12.04 / 14.04 LTS ... but their problem/ solution was on Nvidia Driver. And following that didnt help me!
.
Any solution ?
virtualbox windows freeze
asked Apr 30 at 15:26
Battleseeker_Rex
4116
One more thing, i have the 18.04 live server one for a while .... this happens with it too...... but reason dnt know
– Battleseeker_Rex
Apr 30 at 16:02
Same here. Virtualbox 5.2. Ubuntu 18.04. Windows 10 Host with Intel graphics. Reinstalled thrice. Fails on bootup. No error, it simply waits with a purple screen and 5 dots. No guest additions, it is a fresh install. Trying to login the first time after reboot. Based on the answers, it seems there is no single reason.
– RuntimeException
Jul 13 at 15:26
add a comment |Â
up vote
6
down vote
favorite
up vote
6
down vote
favorite
I am Using Ubuntu in Virtual Box.. the Host OS is Windows10 with dedicated intel's Graphics.
I have reinstalled twice, probably this starts due to sudden shutdown or some reason. Dnt know whats the problem.
Saw a old post about this type on Ubuntu 12.04 / 14.04 LTS ... but their problem/ solution was on Nvidia Driver. And following that didnt help me!
.
Any solution ?
virtualbox windows freeze
asked Apr 30 at 15:26
Battleseeker_Rex
4116
I am Using Ubuntu in Virtual Box.. the Host OS is Windows10 with dedicated intel's Graphics.
I have reinstalled twice, probably this starts due to sudden shutdown or some reason. Dnt know whats the problem.
Saw a old post about this type on Ubuntu 12.04 / 14.04 LTS ... but their problem/ solution was on Nvidia Driver. And following that didnt help me!
.
Any solution ?
virtualbox windows freeze
asked Apr 30 at 15:26
Battleseeker_Rex
4116
asked Apr 30 at 15:26
Battleseeker_Rex
4116
asked Apr 30 at 15:26
Battleseeker_Rex
4116
asked Apr 30 at 15:26
Battleseeker_Rex
4116
4116
One more thing, i have the 18.04 live server one for a while .... this happens with it too...... but reason dnt know
– Battleseeker_Rex
Apr 30 at 16:02
Same here. Virtualbox 5.2. Ubuntu 18.04. Windows 10 Host with Intel graphics. Reinstalled thrice. Fails on bootup. No error, it simply waits with a purple screen and 5 dots. No guest additions, it is a fresh install. Trying to login the first time after reboot. Based on the answers, it seems there is no single reason.
– RuntimeException
Jul 13 at 15:26
add a comment |Â
One more thing, i have the 18.04 live server one for a while .... this happens with it too...... but reason dnt know
– Battleseeker_Rex
Apr 30 at 16:02
Same here. Virtualbox 5.2. Ubuntu 18.04. Windows 10 Host with Intel graphics. Reinstalled thrice. Fails on bootup. No error, it simply waits with a purple screen and 5 dots. No guest additions, it is a fresh install. Trying to login the first time after reboot. Based on the answers, it seems there is no single reason.
– RuntimeException
Jul 13 at 15:26
One more thing, i have the 18.04 live server one for a while .... this happens with it too...... but reason dnt know
– Battleseeker_Rex
Apr 30 at 16:02
One more thing, i have the 18.04 live server one for a while .... this happens with it too...... but reason dnt know
– Battleseeker_Rex
Apr 30 at 16:02
Same here. Virtualbox 5.2. Ubuntu 18.04. Windows 10 Host with Intel graphics. Reinstalled thrice. Fails on bootup. No error, it simply waits with a purple screen and 5 dots. No guest additions, it is a fresh install. Trying to login the first time after reboot. Based on the answers, it seems there is no single reason.
– RuntimeException
Jul 13 at 15:26
Same here. Virtualbox 5.2. Ubuntu 18.04. Windows 10 Host with Intel graphics. Reinstalled thrice. Fails on bootup. No error, it simply waits with a purple screen and 5 dots. No guest additions, it is a fresh install. Trying to login the first time after reboot. Based on the answers, it seems there is no single reason.
– RuntimeException
Jul 13 at 15:26
add a comment |Â
6 Answers
6
active
oldest
votes
up vote
9
down vote
i've had the same issue:
- 3D acceleration = off
- 10 GB Ram
My solution was:
- 1 processor => 4 processors
- enable PAE/NX
answered May 22 at 7:45
Willem Bressers
911
4
I also had to increase the number of processors (I set it to 2). Enabling PAE/NX was not necessary for me.
– Ignitor
Jun 9 at 13:12
Same findings as @Ignitor
– John McCann
Jun 29 at 14:29
@Ignitor worked for me too.. i.e. 2 seemed to suffice
– bph
Jul 6 at 8:34
Adding +1 CPU worked for me.
– MichaelICE
Jul 6 at 18:06
scratch that - still not working for me, well it seems to not freeze randomly once in a blue moon
– bph
Jul 9 at 11:29
 |Â
show 3 more comments
up vote
1
down vote
accepted
In the VirtualBox machine settings, simply turn off the "3D acceleration".
edited Apr 30 at 20:41
ubashu
2,23721736
answered Apr 30 at 17:08
Battleseeker_Rex
4116
1
I already had 3D acceleration turned off, but I did increase the video memory from 16 to 64 Mb and that got it to work for me.
– Chris Chubb
May 8 at 13:57
i have kept my Vid memory full -_- @Chris Chubb
– Battleseeker_Rex
May 9 at 6:10
It was already off for me. Adding a second cpu per bressers answer did the trick.
– HDave
Jul 5 at 15:03
add a comment |Â
up vote
0
down vote
Did you allocate enough RAM to the virtual machine? Give it 2GB or more RAM. I discovered when I ran Ubuntu 18.04 live cd on virtual box, it froze at some point, but on allocation of more RAM, I got it working perfectly
answered Apr 30 at 20:54
belovedk
263
i gave it 4 GB ram .... and 2 core to process from the start .... Turning off the 3d acceleration ... the problem is not repeating now !!!
– Battleseeker_Rex
May 1 at 5:49
Thanks for the tip Though !!
– Battleseeker_Rex
May 1 at 5:50
add a comment |Â
up vote
0
down vote
I had the same problem. When I experienced the problems my settings were:
- RAM 4GB
- CPU 3
- PAE/NX Enabled
- VT-x/AMD-V Enabled
- Nested Paging Enabled
- 3D Acceleration Disabled
- 2D Video Acceleration Disabled
I changed the following settings:
- CPU 1
- PAE/NX Disabled
That made it work.
I changed the following setting:
- PAE/NX Enabled
It still worked.
Looked like there is 'something' with the number of processors. Based on the other answers, there does not seem to be a 'right' number that works for every system.
I then realized that I also have an Ubuntu 18.04 Server VM on my system. This one still works. I noticed that for this virtual machine the Paravirtualization Interface is set to Default, while for my Desktop VM (the one I was having problems with), it was set to Legacy.
I changed it to Default and now it works, with any number of CPU's.
So the solution, for me, was to:
Set Paravirtualization Interface to Default.
answered Jul 9 at 21:44
Jokr
11
add a comment |Â
up vote
0
down vote
It seems like there is no definite answer to this one.
What worked for me is - Uncheck the box labelled "Solid-state Drive" for the virtual hard disk.
3D acceleration is Enabled. 128 MB Video Memory. 4 GB RAM. 2 CPU. Virtualbox Guest Additions are Not installed. All other system settings are at default.
answered Jul 13 at 16:05
RuntimeException
1013
Hi Runtime! Can you explain why disabling the Solid-state Drive ? It's common that the 3d-acceleration can cause freezing.
– abu_bua
Jul 13 at 16:22
Select your VM in manager > Settings > Storage > Select your VDI under SATA > Uncheck the Solid-state Drive box. It is disabled by default. I have an SSD so I had enabled it. Apparently, it is for the guest to see it as an SSD. Seems like there is a bug in Virtualbox 5.2.14 and/or Ubuntu 18.04 where it cannot handle SSD properly.
– RuntimeException
Jul 13 at 16:37
add a comment |Â
up vote
0
down vote
Several of my old VMs seem to hang on bootup. If in Grub I select "recovery mode", the last messages displayed on the screen are:
smp: Bringing up secondary CPUs...
x86: Booting SMP configuration:
Then it hangs.
In my case, I can confirm that for all my VMs experiencing this problem, changing the Virtualbox setting "System -> Acceleration -> Paravirtualization Interface" from "Legacy" to "Default" enabled these old VMs to work again. Switching it back to "Legacy" immediately makes it hang on boot, so I know for certain this is the key to the issue in my case.
answered Aug 19 at 5:36
Stéphane
1,23521225
add a comment |Â
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
9
down vote
i've had the same issue:
- 3D acceleration = off
- 10 GB Ram
My solution was:
- 1 processor => 4 processors
- enable PAE/NX
answered May 22 at 7:45
Willem Bressers
911
4
I also had to increase the number of processors (I set it to 2). Enabling PAE/NX was not necessary for me.
– Ignitor
Jun 9 at 13:12
Same findings as @Ignitor
– John McCann
Jun 29 at 14:29
@Ignitor worked for me too.. i.e. 2 seemed to suffice
– bph
Jul 6 at 8:34
Adding +1 CPU worked for me.
– MichaelICE
Jul 6 at 18:06
scratch that - still not working for me, well it seems to not freeze randomly once in a blue moon
– bph
Jul 9 at 11:29
 |Â
show 3 more comments
up vote
9
down vote
i've had the same issue:
- 3D acceleration = off
- 10 GB Ram
My solution was:
- 1 processor => 4 processors
- enable PAE/NX
answered May 22 at 7:45
Willem Bressers
911
4
I also had to increase the number of processors (I set it to 2). Enabling PAE/NX was not necessary for me.
– Ignitor
Jun 9 at 13:12
Same findings as @Ignitor
– John McCann
Jun 29 at 14:29
@Ignitor worked for me too.. i.e. 2 seemed to suffice
– bph
Jul 6 at 8:34
Adding +1 CPU worked for me.
– MichaelICE
Jul 6 at 18:06
scratch that - still not working for me, well it seems to not freeze randomly once in a blue moon
– bph
Jul 9 at 11:29
 |Â
show 3 more comments
up vote
9
down vote
up vote
9
down vote
i've had the same issue:
- 3D acceleration = off
- 10 GB Ram
My solution was:
- 1 processor => 4 processors
- enable PAE/NX
answered May 22 at 7:45
Willem Bressers
911
i've had the same issue:
- 3D acceleration = off
- 10 GB Ram
My solution was:
- 1 processor => 4 processors
- enable PAE/NX
answered May 22 at 7:45
Willem Bressers
911
answered May 22 at 7:45
Willem Bressers
911
answered May 22 at 7:45
Willem Bressers
911
answered May 22 at 7:45
Willem Bressers
911
911
4
I also had to increase the number of processors (I set it to 2). Enabling PAE/NX was not necessary for me.
– Ignitor
Jun 9 at 13:12
Same findings as @Ignitor
– John McCann
Jun 29 at 14:29
@Ignitor worked for me too.. i.e. 2 seemed to suffice
– bph
Jul 6 at 8:34
Adding +1 CPU worked for me.
– MichaelICE
Jul 6 at 18:06
scratch that - still not working for me, well it seems to not freeze randomly once in a blue moon
– bph
Jul 9 at 11:29
 |Â
show 3 more comments
4
I also had to increase the number of processors (I set it to 2). Enabling PAE/NX was not necessary for me.
– Ignitor
Jun 9 at 13:12
Same findings as @Ignitor
– John McCann
Jun 29 at 14:29
@Ignitor worked for me too.. i.e. 2 seemed to suffice
– bph
Jul 6 at 8:34
Adding +1 CPU worked for me.
– MichaelICE
Jul 6 at 18:06
scratch that - still not working for me, well it seems to not freeze randomly once in a blue moon
– bph
Jul 9 at 11:29
4
4
I also had to increase the number of processors (I set it to 2). Enabling PAE/NX was not necessary for me.
– Ignitor
Jun 9 at 13:12
I also had to increase the number of processors (I set it to 2). Enabling PAE/NX was not necessary for me.
– Ignitor
Jun 9 at 13:12
Same findings as @Ignitor
– John McCann
Jun 29 at 14:29
Same findings as @Ignitor
– John McCann
Jun 29 at 14:29
@Ignitor worked for me too.. i.e. 2 seemed to suffice
– bph
Jul 6 at 8:34
@Ignitor worked for me too.. i.e. 2 seemed to suffice
– bph
Jul 6 at 8:34
Adding +1 CPU worked for me.
– MichaelICE
Jul 6 at 18:06
Adding +1 CPU worked for me.
– MichaelICE
Jul 6 at 18:06
scratch that - still not working for me, well it seems to not freeze randomly once in a blue moon
– bph
Jul 9 at 11:29
scratch that - still not working for me, well it seems to not freeze randomly once in a blue moon
– bph
Jul 9 at 11:29
 |Â
show 3 more comments
up vote
1
down vote
accepted
In the VirtualBox machine settings, simply turn off the "3D acceleration".
edited Apr 30 at 20:41
ubashu
2,23721736
answered Apr 30 at 17:08
Battleseeker_Rex
4116
1
I already had 3D acceleration turned off, but I did increase the video memory from 16 to 64 Mb and that got it to work for me.
– Chris Chubb
May 8 at 13:57
i have kept my Vid memory full -_- @Chris Chubb
– Battleseeker_Rex
May 9 at 6:10
It was already off for me. Adding a second cpu per bressers answer did the trick.
– HDave
Jul 5 at 15:03
add a comment |Â
up vote
1
down vote
accepted
In the VirtualBox machine settings, simply turn off the "3D acceleration".
edited Apr 30 at 20:41
ubashu
2,23721736
answered Apr 30 at 17:08
Battleseeker_Rex
4116
1
I already had 3D acceleration turned off, but I did increase the video memory from 16 to 64 Mb and that got it to work for me.
– Chris Chubb
May 8 at 13:57
i have kept my Vid memory full -_- @Chris Chubb
– Battleseeker_Rex
May 9 at 6:10
It was already off for me. Adding a second cpu per bressers answer did the trick.
– HDave
Jul 5 at 15:03
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
In the VirtualBox machine settings, simply turn off the "3D acceleration".
edited Apr 30 at 20:41
ubashu
2,23721736
answered Apr 30 at 17:08
Battleseeker_Rex
4116
In the VirtualBox machine settings, simply turn off the "3D acceleration".
edited Apr 30 at 20:41
ubashu
2,23721736
answered Apr 30 at 17:08
Battleseeker_Rex
4116
edited Apr 30 at 20:41
ubashu
2,23721736
edited Apr 30 at 20:41
ubashu
2,23721736
edited Apr 30 at 20:41
ubashu
2,23721736
2,23721736
answered Apr 30 at 17:08
Battleseeker_Rex
4116
answered Apr 30 at 17:08
Battleseeker_Rex
4116
answered Apr 30 at 17:08
Battleseeker_Rex
4116
4116
1
I already had 3D acceleration turned off, but I did increase the video memory from 16 to 64 Mb and that got it to work for me.
– Chris Chubb
May 8 at 13:57
i have kept my Vid memory full -_- @Chris Chubb
– Battleseeker_Rex
May 9 at 6:10
It was already off for me. Adding a second cpu per bressers answer did the trick.
– HDave
Jul 5 at 15:03
add a comment |Â
1
I already had 3D acceleration turned off, but I did increase the video memory from 16 to 64 Mb and that got it to work for me.
– Chris Chubb
May 8 at 13:57
i have kept my Vid memory full -_- @Chris Chubb
– Battleseeker_Rex
May 9 at 6:10
It was already off for me. Adding a second cpu per bressers answer did the trick.
– HDave
Jul 5 at 15:03
1
1
I already had 3D acceleration turned off, but I did increase the video memory from 16 to 64 Mb and that got it to work for me.
– Chris Chubb
May 8 at 13:57
I already had 3D acceleration turned off, but I did increase the video memory from 16 to 64 Mb and that got it to work for me.
– Chris Chubb
May 8 at 13:57
i have kept my Vid memory full -_- @Chris Chubb
– Battleseeker_Rex
May 9 at 6:10
i have kept my Vid memory full -_- @Chris Chubb
– Battleseeker_Rex
May 9 at 6:10
It was already off for me. Adding a second cpu per bressers answer did the trick.
– HDave
Jul 5 at 15:03
It was already off for me. Adding a second cpu per bressers answer did the trick.
– HDave
Jul 5 at 15:03
add a comment |Â
up vote
0
down vote
Did you allocate enough RAM to the virtual machine? Give it 2GB or more RAM. I discovered when I ran Ubuntu 18.04 live cd on virtual box, it froze at some point, but on allocation of more RAM, I got it working perfectly
answered Apr 30 at 20:54
belovedk
263
i gave it 4 GB ram .... and 2 core to process from the start .... Turning off the 3d acceleration ... the problem is not repeating now !!!
– Battleseeker_Rex
May 1 at 5:49
Thanks for the tip Though !!
– Battleseeker_Rex
May 1 at 5:50
add a comment |Â
up vote
0
down vote
Did you allocate enough RAM to the virtual machine? Give it 2GB or more RAM. I discovered when I ran Ubuntu 18.04 live cd on virtual box, it froze at some point, but on allocation of more RAM, I got it working perfectly
answered Apr 30 at 20:54
belovedk
263
i gave it 4 GB ram .... and 2 core to process from the start .... Turning off the 3d acceleration ... the problem is not repeating now !!!
– Battleseeker_Rex
May 1 at 5:49
Thanks for the tip Though !!
– Battleseeker_Rex
May 1 at 5:50
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Did you allocate enough RAM to the virtual machine? Give it 2GB or more RAM. I discovered when I ran Ubuntu 18.04 live cd on virtual box, it froze at some point, but on allocation of more RAM, I got it working perfectly
answered Apr 30 at 20:54
belovedk
263
Did you allocate enough RAM to the virtual machine? Give it 2GB or more RAM. I discovered when I ran Ubuntu 18.04 live cd on virtual box, it froze at some point, but on allocation of more RAM, I got it working perfectly
answered Apr 30 at 20:54
belovedk
263
answered Apr 30 at 20:54
belovedk
263
answered Apr 30 at 20:54
belovedk
263
answered Apr 30 at 20:54
belovedk
263
263
i gave it 4 GB ram .... and 2 core to process from the start .... Turning off the 3d acceleration ... the problem is not repeating now !!!
– Battleseeker_Rex
May 1 at 5:49
Thanks for the tip Though !!
– Battleseeker_Rex
May 1 at 5:50
add a comment |Â
i gave it 4 GB ram .... and 2 core to process from the start .... Turning off the 3d acceleration ... the problem is not repeating now !!!
– Battleseeker_Rex
May 1 at 5:49
Thanks for the tip Though !!
– Battleseeker_Rex
May 1 at 5:50
i gave it 4 GB ram .... and 2 core to process from the start .... Turning off the 3d acceleration ... the problem is not repeating now !!!
– Battleseeker_Rex
May 1 at 5:49
i gave it 4 GB ram .... and 2 core to process from the start .... Turning off the 3d acceleration ... the problem is not repeating now !!!
– Battleseeker_Rex
May 1 at 5:49
Thanks for the tip Though !!
– Battleseeker_Rex
May 1 at 5:50
Thanks for the tip Though !!
– Battleseeker_Rex
May 1 at 5:50
add a comment |Â
up vote
0
down vote
I had the same problem. When I experienced the problems my settings were:
- RAM 4GB
- CPU 3
- PAE/NX Enabled
- VT-x/AMD-V Enabled
- Nested Paging Enabled
- 3D Acceleration Disabled
- 2D Video Acceleration Disabled
I changed the following settings:
- CPU 1
- PAE/NX Disabled
That made it work.
I changed the following setting:
- PAE/NX Enabled
It still worked.
Looked like there is 'something' with the number of processors. Based on the other answers, there does not seem to be a 'right' number that works for every system.
I then realized that I also have an Ubuntu 18.04 Server VM on my system. This one still works. I noticed that for this virtual machine the Paravirtualization Interface is set to Default, while for my Desktop VM (the one I was having problems with), it was set to Legacy.
I changed it to Default and now it works, with any number of CPU's.
So the solution, for me, was to:
Set Paravirtualization Interface to Default.
answered Jul 9 at 21:44
Jokr
11
add a comment |Â
up vote
0
down vote
I had the same problem. When I experienced the problems my settings were:
- RAM 4GB
- CPU 3
- PAE/NX Enabled
- VT-x/AMD-V Enabled
- Nested Paging Enabled
- 3D Acceleration Disabled
- 2D Video Acceleration Disabled
I changed the following settings:
- CPU 1
- PAE/NX Disabled
That made it work.
I changed the following setting:
- PAE/NX Enabled
It still worked.
Looked like there is 'something' with the number of processors. Based on the other answers, there does not seem to be a 'right' number that works for every system.
I then realized that I also have an Ubuntu 18.04 Server VM on my system. This one still works. I noticed that for this virtual machine the Paravirtualization Interface is set to Default, while for my Desktop VM (the one I was having problems with), it was set to Legacy.
I changed it to Default and now it works, with any number of CPU's.
So the solution, for me, was to:
Set Paravirtualization Interface to Default.
answered Jul 9 at 21:44
Jokr
11
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I had the same problem. When I experienced the problems my settings were:
- RAM 4GB
- CPU 3
- PAE/NX Enabled
- VT-x/AMD-V Enabled
- Nested Paging Enabled
- 3D Acceleration Disabled
- 2D Video Acceleration Disabled
I changed the following settings:
- CPU 1
- PAE/NX Disabled
That made it work.
I changed the following setting:
- PAE/NX Enabled
It still worked.
Looked like there is 'something' with the number of processors. Based on the other answers, there does not seem to be a 'right' number that works for every system.
I then realized that I also have an Ubuntu 18.04 Server VM on my system. This one still works. I noticed that for this virtual machine the Paravirtualization Interface is set to Default, while for my Desktop VM (the one I was having problems with), it was set to Legacy.
I changed it to Default and now it works, with any number of CPU's.
So the solution, for me, was to:
Set Paravirtualization Interface to Default.
answered Jul 9 at 21:44
Jokr
11
I had the same problem. When I experienced the problems my settings were:
- RAM 4GB
- CPU 3
- PAE/NX Enabled
- VT-x/AMD-V Enabled
- Nested Paging Enabled
- 3D Acceleration Disabled
- 2D Video Acceleration Disabled
I changed the following settings:
- CPU 1
- PAE/NX Disabled
That made it work.
I changed the following setting:
- PAE/NX Enabled
It still worked.
Looked like there is 'something' with the number of processors. Based on the other answers, there does not seem to be a 'right' number that works for every system.
I then realized that I also have an Ubuntu 18.04 Server VM on my system. This one still works. I noticed that for this virtual machine the Paravirtualization Interface is set to Default, while for my Desktop VM (the one I was having problems with), it was set to Legacy.
I changed it to Default and now it works, with any number of CPU's.
So the solution, for me, was to:
Set Paravirtualization Interface to Default.
answered Jul 9 at 21:44
Jokr
11
answered Jul 9 at 21:44
Jokr
11
answered Jul 9 at 21:44
Jokr
11
answered Jul 9 at 21:44
Jokr
11
11
add a comment |Â
add a comment |Â
up vote
0
down vote
It seems like there is no definite answer to this one.
What worked for me is - Uncheck the box labelled "Solid-state Drive" for the virtual hard disk.
3D acceleration is Enabled. 128 MB Video Memory. 4 GB RAM. 2 CPU. Virtualbox Guest Additions are Not installed. All other system settings are at default.
answered Jul 13 at 16:05
RuntimeException
1013
Hi Runtime! Can you explain why disabling the Solid-state Drive ? It's common that the 3d-acceleration can cause freezing.
– abu_bua
Jul 13 at 16:22
Select your VM in manager > Settings > Storage > Select your VDI under SATA > Uncheck the Solid-state Drive box. It is disabled by default. I have an SSD so I had enabled it. Apparently, it is for the guest to see it as an SSD. Seems like there is a bug in Virtualbox 5.2.14 and/or Ubuntu 18.04 where it cannot handle SSD properly.
– RuntimeException
Jul 13 at 16:37
add a comment |Â
up vote
0
down vote
It seems like there is no definite answer to this one.
What worked for me is - Uncheck the box labelled "Solid-state Drive" for the virtual hard disk.
3D acceleration is Enabled. 128 MB Video Memory. 4 GB RAM. 2 CPU. Virtualbox Guest Additions are Not installed. All other system settings are at default.
answered Jul 13 at 16:05
RuntimeException
1013
Hi Runtime! Can you explain why disabling the Solid-state Drive ? It's common that the 3d-acceleration can cause freezing.
– abu_bua
Jul 13 at 16:22
Select your VM in manager > Settings > Storage > Select your VDI under SATA > Uncheck the Solid-state Drive box. It is disabled by default. I have an SSD so I had enabled it. Apparently, it is for the guest to see it as an SSD. Seems like there is a bug in Virtualbox 5.2.14 and/or Ubuntu 18.04 where it cannot handle SSD properly.
– RuntimeException
Jul 13 at 16:37
add a comment |Â
up vote
0
down vote
up vote
0
down vote
It seems like there is no definite answer to this one.
What worked for me is - Uncheck the box labelled "Solid-state Drive" for the virtual hard disk.
3D acceleration is Enabled. 128 MB Video Memory. 4 GB RAM. 2 CPU. Virtualbox Guest Additions are Not installed. All other system settings are at default.
answered Jul 13 at 16:05
RuntimeException
1013
It seems like there is no definite answer to this one.
What worked for me is - Uncheck the box labelled "Solid-state Drive" for the virtual hard disk.
3D acceleration is Enabled. 128 MB Video Memory. 4 GB RAM. 2 CPU. Virtualbox Guest Additions are Not installed. All other system settings are at default.
answered Jul 13 at 16:05
RuntimeException
1013
edited Jul 13 at 16:34
answered Jul 13 at 16:05
RuntimeException
1013
answered Jul 13 at 16:05
RuntimeException
1013
answered Jul 13 at 16:05
RuntimeException
1013
1013
Hi Runtime! Can you explain why disabling the Solid-state Drive ? It's common that the 3d-acceleration can cause freezing.
– abu_bua
Jul 13 at 16:22
Select your VM in manager > Settings > Storage > Select your VDI under SATA > Uncheck the Solid-state Drive box. It is disabled by default. I have an SSD so I had enabled it. Apparently, it is for the guest to see it as an SSD. Seems like there is a bug in Virtualbox 5.2.14 and/or Ubuntu 18.04 where it cannot handle SSD properly.
– RuntimeException
Jul 13 at 16:37
add a comment |Â
Hi Runtime! Can you explain why disabling the Solid-state Drive ? It's common that the 3d-acceleration can cause freezing.
– abu_bua
Jul 13 at 16:22
Select your VM in manager > Settings > Storage > Select your VDI under SATA > Uncheck the Solid-state Drive box. It is disabled by default. I have an SSD so I had enabled it. Apparently, it is for the guest to see it as an SSD. Seems like there is a bug in Virtualbox 5.2.14 and/or Ubuntu 18.04 where it cannot handle SSD properly.
– RuntimeException
Jul 13 at 16:37
Hi Runtime! Can you explain why disabling the Solid-state Drive ? It's common that the 3d-acceleration can cause freezing.
– abu_bua
Jul 13 at 16:22
Hi Runtime! Can you explain why disabling the Solid-state Drive ? It's common that the 3d-acceleration can cause freezing.
– abu_bua
Jul 13 at 16:22
Select your VM in manager > Settings > Storage > Select your VDI under SATA > Uncheck the Solid-state Drive box. It is disabled by default. I have an SSD so I had enabled it. Apparently, it is for the guest to see it as an SSD. Seems like there is a bug in Virtualbox 5.2.14 and/or Ubuntu 18.04 where it cannot handle SSD properly.
– RuntimeException
Jul 13 at 16:37
Select your VM in manager > Settings > Storage > Select your VDI under SATA > Uncheck the Solid-state Drive box. It is disabled by default. I have an SSD so I had enabled it. Apparently, it is for the guest to see it as an SSD. Seems like there is a bug in Virtualbox 5.2.14 and/or Ubuntu 18.04 where it cannot handle SSD properly.
– RuntimeException
Jul 13 at 16:37
add a comment |Â
up vote
0
down vote
Several of my old VMs seem to hang on bootup. If in Grub I select "recovery mode", the last messages displayed on the screen are:
smp: Bringing up secondary CPUs...
x86: Booting SMP configuration:
Then it hangs.
In my case, I can confirm that for all my VMs experiencing this problem, changing the Virtualbox setting "System -> Acceleration -> Paravirtualization Interface" from "Legacy" to "Default" enabled these old VMs to work again. Switching it back to "Legacy" immediately makes it hang on boot, so I know for certain this is the key to the issue in my case.
answered Aug 19 at 5:36
Stéphane
1,23521225
add a comment |Â
up vote
0
down vote
Several of my old VMs seem to hang on bootup. If in Grub I select "recovery mode", the last messages displayed on the screen are:
smp: Bringing up secondary CPUs...
x86: Booting SMP configuration:
Then it hangs.
In my case, I can confirm that for all my VMs experiencing this problem, changing the Virtualbox setting "System -> Acceleration -> Paravirtualization Interface" from "Legacy" to "Default" enabled these old VMs to work again. Switching it back to "Legacy" immediately makes it hang on boot, so I know for certain this is the key to the issue in my case.
answered Aug 19 at 5:36
Stéphane
1,23521225
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Several of my old VMs seem to hang on bootup. If in Grub I select "recovery mode", the last messages displayed on the screen are:
smp: Bringing up secondary CPUs...
x86: Booting SMP configuration:
Then it hangs.
In my case, I can confirm that for all my VMs experiencing this problem, changing the Virtualbox setting "System -> Acceleration -> Paravirtualization Interface" from "Legacy" to "Default" enabled these old VMs to work again. Switching it back to "Legacy" immediately makes it hang on boot, so I know for certain this is the key to the issue in my case.
answered Aug 19 at 5:36
Stéphane
1,23521225
Several of my old VMs seem to hang on bootup. If in Grub I select "recovery mode", the last messages displayed on the screen are:
smp: Bringing up secondary CPUs...
x86: Booting SMP configuration:
Then it hangs.
In my case, I can confirm that for all my VMs experiencing this problem, changing the Virtualbox setting "System -> Acceleration -> Paravirtualization Interface" from "Legacy" to "Default" enabled these old VMs to work again. Switching it back to "Legacy" immediately makes it hang on boot, so I know for certain this is the key to the issue in my case.
answered Aug 19 at 5:36
Stéphane
1,23521225
answered Aug 19 at 5:36
Stéphane
1,23521225
answered Aug 19 at 5:36
Stéphane
1,23521225
answered Aug 19 at 5:36
Stéphane
1,23521225
1,23521225
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1030181%2fubuntu-18-04-lts-freezes-while-in-boot-in-wndows-virtual-box-solution%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
One more thing, i have the 18.04 live server one for a while .... this happens with it too...... but reason dnt know
– Battleseeker_Rex
Apr 30 at 16:02
Same here. Virtualbox 5.2. Ubuntu 18.04. Windows 10 Host with Intel graphics. Reinstalled thrice. Fails on bootup. No error, it simply waits with a purple screen and 5 dots. No guest additions, it is a fresh install. Trying to login the first time after reboot. Based on the answers, it seems there is no single reason.
– RuntimeException
Jul 13 at 15:26