Ubuntu 21.10 no longer starts in VM (virtualbox)

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Peter798
Posts: 2
Joined: 25. Jan 2022, 22:47

Ubuntu 21.10 no longer starts in VM (virtualbox)

Post by Peter798 »

A few months ago i've installed an ubuntu 21.10 virtual machine and the machine was working well. Today i wanted to boot it again but the boot process is stuck to this error with a black screen (image in the zip file). I've searched online to try fixing this kind of problem with unfortunately no result. I leave the log file into the zip file.


thanks to all responding , i really need to boot it.
Attachments
VM-log-error.zip
(23.06 KiB) Downloaded 13 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu 21.10 no longer starts in VM (virtualbox)

Post by mpack »

The error message shown in your screen is AFAIK perfectly normal, certainly not a VirtualBox error.

I have a number of settings changes to suggest:
  1. Increasing VM RAM from 1024MB to 2048MB.
  2. Allocate 2 CPU cores.
  3. Allocate 128MB graphics RAM.
You then should update the Guest Additions, which are horrifically out of date (running 6.1.32 on the host, 6.0.0 GAs in the guest).
Peter798
Posts: 2
Joined: 25. Jan 2022, 22:47

Re: Ubuntu 21.10 no longer starts in VM (virtualbox)

Post by Peter798 »

thanks for your answer, i've changed these settings but it's always stuck on a black screen now :(
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu 21.10 no longer starts in VM (virtualbox)

Post by fth0 »

I'd suggest to check if your 10 GB virtual disk is full.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu 21.10 no longer starts in VM (virtualbox)

Post by mpack »

And please note that we rarely accept assurances as to the current state in your VM: we would need to see another zipped log file showing all of the above issues corrected.
Post Reply