virtualbox.org

Hi,

it seems to be not the only one which i faced this issue but i am still not able to solve this issue by my own.I use Virtualbox 6.1.32 r149290 on Win10(host OS) and i have been using my Ubuntu VM without any issues for a long time.Basically i use 2 VMs with the specs below:

VM1 which works:

Code: Select all

VirtualBox VM 6.1.32 r149290 win.amd64 (Jan 17 2022 11:29:30) release log
Log opened 2022-03-29T19:37:28.524990900Z
Build Type: release
OS Product: Windows 10
OS Release: 10.0.19044
OS Service Pack: 

VBoxService 6.1.10 r138449 (verbosity: 0) linux.amd64 (Jun  4 2020 18:43:22) release log
Log opened 2022-03-29T19:38:55.617025000Z
OS Product: Linux
OS Release: 5.4.0-105-generic
OS Version: #119~18.04.1-Ubuntu SMP Tue Mar 8 11:21:24 UTC 2022
Executable: /opt/VBoxGuestAdditions-6.1.10/sbin/VBoxService
Process ID: 2704
Package type: LINUX_64BITS_GENERIC
6.1.10 r138449 started. Verbose level = 0

VMMDev: Guest Additions information report: Version 6.1.10 r138449 '6.1.10'
VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00053100 (Linux >= 2.6, 64-bit)

VM2 which stopped working

Code: Select all

VirtualBox VM 6.1.32 r149290 win.amd64 (Jan 17 2022 11:29:30) release log
Log opened 2022-03-29T19:27:02.092221600Z
Build Type: release
OS Product: Windows 10
OS Release: 10.0.19044
OS Service Pack: 

VBoxService 6.1.22 r144080 (verbosity: 0) linux.amd64 (Apr 28 2021 18:43:39) release log
Log opened 2022-03-29T19:27:19.948340000Z
OS Product: Linux
OS Release: 5.13.0-28-generic
OS Version: #31~20.04.1-Ubuntu SMP Wed Jan 19 14:08:10 UTC 2022
Executable: /opt/VBoxGuestAdditions-6.1.22/sbin/VBoxService
Process ID: 716
Package type: LINUX_64BITS_GENERIC
6.1.22 r144080 started. Verbose level = 0

VMMDev: Guest Additions information report: Version 6.1.22 r144080 '6.1.22'
VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00053100 (Linux >= 2.6, 64-bit)

I analysed the Log from VM1 and compared it with log from VM2 but did not find anything suspicious.VM2 was working fine but it stopped working and i think this happen after win10 update,at least this is i think an event that might trigger this.Basically VM2 is started but guest host can not load the gui,i see just a black screen.I tried all these steps:
1.allocating 128 MB VRAM
2.provide 2 vCPUs to a guest OS
3.disable 3D Acceleration
but it did not help.

Attached you can find the logs.I also tried to start the VM with option "Detachable start" and VM is able to boot.Any idea about this issue?

Many thanks in advance
olti88

Your host's Hyper-V is enabled, which may or may not be a problem. But the logs were taken while the VM window was still open, so the diagnostic info we need is missing.

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

Hi,

i attached again the logs.Hyper-V should not be the RCA because the other VM is running fine.

olti88 wrote:Hyper-V should not be the RCA

I agree. The log does not show the recent Hyper-V offset bug.

The log does show what appears to be a working VM environment.

Ubuntu is known to go blackscreen if there is not enough free disk space to start the desktop environment. This happens in real PCs too. The solution is to log on text-only and delete stuff until the desktop environment can start. Also see How to Resize a Drive.

i don't think the disk space is the problem because it has enough free space

: free space.JPG (24.59 KiB) Viewed 34973 times

: free space1.png (10.76 KiB) Viewed 34973 times

Is there any known bug with constellation Ubuntu 20.04 / Virtual Box 6.1.22 r144080 / Guest Additions Version 6.1.22 ?
Is there any way to start linux in Vbox without gui?

The first picture only shows the existing and final size of the VM's disk file. It doesn't necessarily reflect the available partition space inside the VM.

The bottom picture looks like it comes from a Linux OS, but the host is Windows. How did you get that screenshot?

FWIW Ubuntu filling up and Hyper-V getting in the way are the only ways I know of to cause Ubuntu blackscreening. Since the VM 'hardware' seems to be working correctly, and the VM OS is starting the Guest Additions, you might have to log into the VM text-only and see why the desktop environment isn't starting.

olti88 wrote:Is there any known bug with constellation Ubuntu 20.04 / Virtual Box 6.1.22 r144080 / Guest Additions Version 6.1.22 ?

Not a bug, but a well-known issue: Linux kernel 5.13 is only supported by VirtualBox 6.1.24 and newer. While your VirtualBox 6.1.32 is newer, your VirtualBox Guest Additions 6.1.22 are not.

scottgus1 wrote:The bottom picture looks like it comes from a Linux OS, but the host is Windows. How did you get that screenshot?

In a terminal, olti88 used the df -h command to show information about the disk free space with human readable output, to show that the Linux root file system has ample free space.

virtualbox.org

Ubuntu VM hangs on black screen

Ubuntu VM hangs on black screen

Re: Ubuntu VM hangs on black screen

Re: Ubuntu VM hangs on black screen

Re: Ubuntu VM hangs on black screen

Re: Ubuntu VM hangs on black screen

Re: Ubuntu VM hangs on black screen

Re: Ubuntu VM hangs on black screen