ISO 18.1.5 - VirtualBox loading time - 'black screen of death'

How exactly would one go about replicating this issue?


❯ inxi -SCG --no-host
  Kernel: 4.19.92-1-MANJARO x86_64 bits: 64 Desktop: Openbox 3.6.1 
  Distro: Manjaro Linux 
  Topology: Quad Core model: Intel Core i5-4570 bits: 64 type: MCP 
  L2 cache: 6144 KiB 
  Speed: 798 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 801 2: 819 
  3: 805 4: 801 
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  driver: i915 v: kernel 
  Display: x11 server: X.Org 1.20.6 driver: intel 
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.3.1 

VBox VM guest

  • 2 VCPU
  • 2 GB RAM
  • 128M graphics
  • EFI

ISOs used

Switching between VBoxSVGA and VMSVGA (no installation)

  • VBoxSVGA takes +4m to load
  • VMSVGA is ready in less than 30s

Arch based PacBang load times do not change significantly - the only difference between the graphic modes is screen resizing.

There is definitely some off with VirtualBox in general. For Linux they recommend VMware graphics and the other VGAs are for Windows only. We may test an ISO with linux419 as kernel.

Maybe it's viable to combine my virtualmachine mhwd fixes with my one line guest modules screen-resize fix (I already tested that combination. Works great with vmsvga). I doubt upstream will adopt the latter for the reasons outlined in the third comment.

Can you also reproduce this with my mhwd fixes ISO? I've tried your settings and I can't reproduce it using my ISO. I'll download the XFCE ISO in the meantime.

That one is ok. Comes up immediately.

1 Like

Yep I can reproduce that with the XFCE ISO, but not with my mhwd-fixes kde ISO. I'll build an XFCE ISO with mhwd fixes for testing this.

1 Like

My xfce ISO with mhwd fixes which were merged doesn't seem to have this problem. I don't know why, maybe just a slightly broken ISO?

I am experiencing this problem too.
I've shared details here:

We will have those fixes in our 19.0 releases.


Forum kindly sponsored by