virtualbox.org

Hi

I'm trying to run ubuntu-20.04.3-desktop-amd64 in VirtualBox 6.12 (Version 6.1.32 r149290 (Qt5.6.2) running in Windows 10 Pro
I'm facing a lot of problems. I've tried several times. When I'm installing, every seems to work fine. But when installation is done, I use to face a black screen once ubuntu loading screen has passed. I've tried everything, enabling and disabling 3D acceleration, sometimes it works with it enable and sometimes with it disabled.
It's matter of luck that it runs displaying desktop. But even when this happens, it uses to have a bad behavior. When I try to run firefox , it takes ages.
If I set Graphic controller to VBoxSVGA instead of VMSVGA it works with a poor resolution. I've already installed tools and restarted my host machine several times. But no luck.
Could anyone help me? I'm starting to be desperate. I suspect it's related with graphic compatibility, but not sure.

Thanks a lot for your help

Attached you can find VBox log latest time it failed and also a virtualized system configuration.

You only provided a partial log. Please provide the complete log - which will fit if zipped.

Hi, what version of Windows 10 are you using?, I'm using version 21H2 (10.0.19044) and I'm having the same Blank screen with Centos even with a fresh installation.

I need to mention that Centos starts but never completes.

Due to the comments about logs I found the following in the VBoxSVC.log:

ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37

Hope this info helps.

ranrodrig wrote: ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37

This message is found in almost every log, and does not indicate a real error. It simply means that the managers VM preview window can't work, usually because the VM is transitioning through non-graphical display modes.

mpack wrote:You only provided a partial log. Please provide the complete log - which will fit if zipped.

Sorry. I think I had included the whole log. Let me try it again.

ranrodrig wrote:what version of Windows 10 are you using?,

Windows 10 Pro 21H2 (19044.1526)

Thank you all for your help.

xaruman wrote: Sorry. I think I had included the whole log. Let me try it again.

A common mistake is to grab the log while the VirtualBox VM is still running and therefore still has the log file opened. If the VM window or an error dialog is still being displayed then the VM is still running.

mpack wrote:

xaruman wrote: Sorry. I think I had included the whole log. Let me try it again.

A common mistake is to grab the log while the VirtualBox VM is still running and therefore still has the log file opened. If the VM window or an error dialog is still being displayed then the VM is still running.

Thanks for your tips. I hope now it's ok.

Yes thanks, the log now covers the entire run time (and termination).

You are over committing host RAM and CPU cores (in the latter case you leave nothing for the host). I would reduce VAM RAM to 10GB (10240MB) max, and reduce CPU cores to 2.

00:00:02.988376 Host RAM: 32418MB (31.6GB) total, 15373MB (15.0GB) available
00:00:04.794981 CPUM: Physical host cores: 4
...
00:00:03.310813 RamSize <integer> = 0x0000000400000000 (17 179 869 184, 16 384 MB, 16.0 GB)
00:00:03.310811 NumCPUs <integer> = 0x0000000000000004 (4)

You should also enable 3D (hardware graphics) acceleration: a 2.5K graphics mode is rather a stretch for a software only GPU simulation.

mpack wrote:Yes thanks, the log now covers the entire run time (and termination).

You are over committing host RAM and CPU cores (in the latter case you leave nothing for the host). I would reduce VAM RAM to 10GB (10240MB) max, and reduce CPU cores to 2.

00:00:02.988376 Host RAM: 32418MB (31.6GB) total, 15373MB (15.0GB) available
00:00:04.794981 CPUM: Physical host cores: 4
...
00:00:03.310813 RamSize <integer> = 0x0000000400000000 (17 179 869 184, 16 384 MB, 16.0 GB)
00:00:03.310811 NumCPUs <integer> = 0x0000000000000004 (4)

You should also enable 3D (hardware graphics) acceleration: a 2.5K graphics mode is rather a stretch for a software only GPU simulation.

Thanks for your help. I thought that just setting half or resources should work. But maybe 4 cores are too much :sweat
I've tried running with 3D acceleration but another black screen. Without it enabled it started, but it's continuously displaying an error message which I cannot see complete due to it's cut and I don't know where to check. It says "VBoxClient: Failure waiting for event, rc=VERR_INVALID_"
Rest of system seems to work fine. I will investigate further how to fix that annoying pop up window.

Thanks a lot for your help mpack

mpack wrote:Yes thanks, the log now covers the entire run time (and termination).

You are over committing host RAM and CPU cores (in the latter case you leave nothing for the host). I would reduce VAM RAM to 10GB (10240MB) max, and reduce CPU cores to 2.

00:00:02.988376 Host RAM: 32418MB (31.6GB) total, 15373MB (15.0GB) available
00:00:04.794981 CPUM: Physical host cores: 4
...
00:00:03.310813 RamSize <integer> = 0x0000000400000000 (17 179 869 184, 16 384 MB, 16.0 GB)
00:00:03.310811 NumCPUs <integer> = 0x0000000000000004 (4)

You should also enable 3D (hardware graphics) acceleration: a 2.5K graphics mode is rather a stretch for a software only GPU simulation.

It looked like it worked. But when I've restarted system once system updates have been applied. Same black screen situation. Attaching latest logs.
I've changed memory to 10GB and also number of cpus to 2. Still not lucky enough

Thanks for your help. I really appreciate it.

xaruman wrote:I've restarted system once system updates have been applied. Same black screen

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

The VM has a 100GB drive. Anything is possible but I'd be surprised if this was lack of disk space.

Thanks for your help. But I don't think it can be related.
This is df info when it works (once every 10 tries...)
"df -h"
Filesystem Size Used Avail Use% Mounted on
udev 4,9G 0 4,9G 0% /dev
tmpfs 996M 1,4M 995M 1% /run
/dev/sda5 98G 14G 79G 15% /
tmpfs 4,9G 0 4,9G 0% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 4,9G 0 4,9G 0% /sys/fs/cgroup
/dev/loop0 56M 56M 0 100% /snap/core18/2128
/dev/loop1 51M 51M 0 100% /snap/snap-store/547
/dev/loop2 66M 66M 0 100% /snap/gtk-common-themes/1515
/dev/loop5 55M 55M 0 100% /snap/snap-store/558
/dev/loop3 219M 219M 0 100% /snap/gnome-3-34-1804/72
/dev/loop4 62M 62M 0 100% /snap/core20/1376
/dev/loop7 128K 128K 0 100% /snap/bare/5
/dev/loop6 66M 66M 0 100% /snap/gtk-common-themes/1519
/dev/loop8 219M 219M 0 100% /snap/gnome-3-34-1804/77
/dev/loop9 249M 249M 0 100% /snap/gnome-3-38-2004/99
/dev/loop10 62M 62M 0 100% /snap/core20/1361
/dev/loop11 56M 56M 0 100% /snap/core18/2284
/dev/loop12 95M 95M 0 100% /snap/go/9028
/dev/loop13 95M 95M 0 100% /snap/go/9360
/dev/loop14 44M 44M 0 100% /snap/snapd/14978
/dev/sda1 511M 4,0K 511M 1% /boot/efi
tmpfs 996M 20K 996M 1% /run/user/1000
/dev/loop15 44M 44M 0 100% /snap/snapd/15177

Once I've updated OS (just in case problems could be related with OS status) and updating VMBox tools. It has stuck. I think due to I clicked close to VM's window boundary, but I've also tried running full screen and same result. It's too unstable.
Attached you can find latest log also, just in case something new could be deduced.

Thanks for your time and help

Sorry to post, I didn't see a way to add myself to responses for this thread. I also spent ½ day going many rounds with this issue while attempting to install Ubuntu 20.04.4 LTS x64

Machine: SurfaceBook 32GB RAM, Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz 1.50 GHz, Windows 10 Professional
VirtualBox: 6.1.32 with extension pack
Definition: Ubuntu; 2-Cores, 4GB RAM, 32GB VDI.

I finally downloaded Ubuntu_20.04.4_VB_LinuxVMImages.COM and it appears to work. Would like to know why, but afraid to look a gift horse in the mouth.

During my attempts, I saw many console errors about not being able to log messages which lead me to believe that sending you my logs would be a worthless effort.
Other things I noticed when I appeared to have success, I had keyboard bounce which was so bad I couldn't type my login password correctly, and after about 15 minutes the screen would go blank and the VM machine appeared to be locked up. The BusyBox installer seemed to work fine during installation.

This is the stock release ubuntu-20.04.4-desktop-amd64.iso selected automagically for me from Ubuntu's site.