Black screen since upgrading to VirtualBox 6.0.10-1

[Mickael]

Hello,

Monday I upgraded VirtualBox to the 6.0.10-1, and my guest system (windows 7 64 bit) don't start anymore. When I start it, I juste have a black screen, and nothing happen.
I'm using the VirtualBox since January and never got any problem on it.
I have already checked the 3D accélération (disanable), checked in the bioss that VT-X is enable, checked solution on the net, nothing work,...

On the log I have this error:

ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37

but, don't understand it...

Host: Manjaro
Guest: W7 64 bit

Thank you for the help!

[socratis]

Let's start with the easy ones...

00:00:04.015520 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87}
                aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)},
                preserve=false aResultDetail=-37

The error that you're getting is a red herring, it means that the "Preview" window in VirtualBox Manager couldn't be updated. We should talk to the developers to make this a "WARNING", lots of people interpret it the wrong way.

00:00:00.774857 VirtualBox VM 6.0.10 r132055 linux.amd64 (Jul 16 2019 13:49:20) release log
00:00:00.924215   Oracle VM VirtualBox Extension Pack (Version: 6.0.0 r127566; VRDE Module: VBoxVRDP)

You updated VirtualBox, but not the ExtPack. It's a miracle that the VM is even running! Please update the ExtPack to match the main program version.

00:00:02.048027 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:03.478360 CPUM: Physical host cores: 4
00:00:03.478740 Full Name: "Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz"

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). See "CPU Cores versus threads" and "Why is it a bad idea to allocate as many VCPUs as there are physical CPUs?".

Just check the link for your CPU above, and make sure you read the text in the "?" next to the "# of Cores" and "# of Threads" in that Intel page...

00:00:02.048186 [/Devices/usb-xhci/] (level 2)

There's no native support for USB3 on Win7. Have you install the appropriate drivers? See USB basics and troubleshooting » #6: Guest support.

00:00:02.048205 VMSVGA3dEnabled    <integer> = 0x0000000000000000 (0)
00:00:02.048206 VMSVGAEnabled      <integer> = 0x0000000000000001 (1)
00:00:02.048206 VRamSize           <integer> = 0x0000000004000000 (67 108 864, 64 MB)

Shut down the VM. Go to the VM Settings » Display » Screen. Enable 3D acceleration. Maximize the VRAM to 256 MB.

For future reference, you should completely shut down the VM before grabbing the VBox.log. Then ZIP it before attaching it to your response.

[Mickael]

Hello Socratis!

Thank you a lot to trying helping me.

In the two last week I was busy but I was still trying to find a solution by myself.
I updated the extension pack after posting the first post with the log file. The problem is not there.
I changed the physical host core to 2. Still having the black screen.
Yes, I have the USB3 driver installed on the W7 guest.
I enabled 3D acceleration and maximized the VRAM to 256 MB. Still black screen.

What I have tryed by myself:
_ I tested the guest machine on another computer: it work fine.
_ I removed VB and all directories (config, kernel module,...) and installed it again. Still black screen.
_ I tryed to install VB 5.2.28: still black screen.

I'm thinking to try to downgrade my kernel linux 5.2 to 4.19, dellect again VB and all directories and installing it again (using of course the right kernel module).

Every time that I start the guest machine and having the black screen, I close the guest by the window's guest and VB crash. I have to restart my computer to be able to start VB again. And my manjaro crash too when closing it "GDbus.Error:org.freedesktop.Dbus.Error.InvalidArgs". I don't have this error when not opening VB.

I'm sending you again the Vbox log.

Sorry for my bad english .

[fth0]

You updated VirtualBox, but not the ExtPack. It's a miracle that the VM is even running! Please update the ExtPack to match the main program version.

@Mickael:
Now you updated the ExtPack, but not VirtualBox. Please reread socratis comment again, especially the underlined word.

[socratis]

That's absolutely correct:

00:00:01.229013 VirtualBox VM 6.0.10 r132055 linux.amd64 (Jul 16 2019 13:49:20) release log
00:00:01.299759   Oracle VM VirtualBox Extension Pack (Version: 6.0.12 r133076; VRDE Module: VBoxVRDP)