virtualbox.org

It happens in 5.2.30 as well.
Is it resolved in 6.0.8, and will the referenced ticket be updated once a new release is confirmed to fix this?

I am having this problem with Windows 10 hosts 1809 and 1903 and Windows 10 guests 1809 and 1903 in all combinations with virtual box 5.2.28 and 5.2.30 and number of versions 6.0.X including latest 6.0.8.
Guest works well for a period of time but then screen goes black and guest stops responding to user input. ACPI shutdown doesn't work. Changing screen resolution seems to work but black screen remains.
I have tried using VBoxVGA and VBoxSVGA as display adapters and issue is still present.
I have tried disabling 3d acceleration but than display in guest does not update for seconds at a time so this is even worse.
Attached the log generated on vb 6.0.8 windows 10 host 1809 and guest 1903.

dmz73 wrote:Attached the log generated on vb 6.0.8 windows 10 host 1809 and guest 1903.

I'm afraid you didn't attach the log...

Just to add my voice, I saw that behavior too with my Win10-64 1607 VM.

I just put some fresh logs from 6.0.8 / 6.0.9 (130520, 130970) and 5.2.30 / 5.2.31 (130521, 130893) into the attached ticket. The main issue is still here, even if I see fewer warnings now.

@socratis: Your main (and probably only) host system is different macOS versions, but you also have this behavior in all of your Windows 10 guests? So it isn’t specific to the Windows host and guest combination?

Air Force One wrote:@socratis: Your main (and probably only) host system is different macOS versions

No, I have 3 computers, that can run: 10.9, 10.11, 10.12, 10.13, 10.14, Win7-32, Win7-64, Win10-64, Mint19-64, at will. But you do realize that getting a result matrix like that takes a significant time investment on my part, and currently I can't afford it.

Heck, I haven't managed to install 10.14 as a VM yet, and that's definitely a higher priority for me...

I can confirm this affects me on VirtualBox 5.2.30, Windows 10 Professional 1809 32bit, at bootup it often takes almost a minute for GUI to appear. Debian Jessie Host x86_64 kernel 4.9.

@tjahns
This is not the same thing. We're talking about a VM that's already running, not a VM that's slow to start up. Please open a new thread with your problem and read the thread Minimum information needed for assistance.

I managed to fix the issue! Disabling sleep mode was not an option for me and after waiting for over a month for a patch I found this solution:
1. install Parallels
2. migrate VirtualBox machines to Parallels
3. Uninstall Virtualbox

Everything seems to work fine for now. No black screen when guest Windows 10 returns from sleep.

rzz wrote:I managed to fix the issue!

Seriously now? Are you kidding me? Is this in the 'troll' category?

<troll>
Hey buddy, thank you for a nice solution of this bug, really appreciated it! Just one question: because I still have not enough money for Mac (I really tried it hard, even get all my empty bottles back, but deposit didn’t help much here), I’m looking for a Parallels version for Windows. But I still can’t find it! Can you give me a link to the Parallels for Windows, so I could test your solution on my computer?
</troll>

@socratis: You have to admit, that this was hilarious, I laughed very hard.

@All This is fixed in the version 6.0.9-131597, but not in 5.2.31-131558 .

Good one!

Air Force One wrote:This is fixed in the version 6.0.9-131597, but not in 5.2.31-131558

I think it's fixed too, as you saw from my response to the ticket, and as far as 5.2.31, notice that it's behind the 6.0.9 build, so maybe the fix is somewhere in between and you should wait for the next 5.2.31 build to see if it's actually backported or it simply didn't make it for the r131558 one?

If you are using a device with low CPU you will probably experience this

@Tryberless
This has nothing to do with a powerful or not CPU. This is a legitimate bug which has been addressed and fixed.