virtualbox.org

Hello all,

My host is Mac OS 10.9.1. VirtualBox is at 4.3.8. Prior to installing guest additions I had no video issues. After installing them, my 8.1 guest works fine until either the guest turns the display off due to power saving functionality or the Mac turns its display off. I disabled all power saving features on the guest (display no longer powers down, hard disks are not powered off, etc) but after OS X puts the Mac's display to sleep, the screen goes black on the VM and never comes back. Neither 2D or 3D acceleration is enabled and I have 128 MB of RAM allocated to the display adapter.

Any ideas?

First off, what's the GUEST OS?
What if you try switching out of fullscreen (HOST+F) and into fullscreen again, after the VM screen blackout happens? Doesn't it come back?

thanar wrote:First off, what's the GUEST OS?
What if you try switching out of fullscreen (HOST+F) and into fullscreen again, after the VM screen blackout happens? Doesn't it come back?

Windows 8.1 is the guest. Mac OS 10.9.2 is the host. I'll try switching in and out of full screen and report back shortly.

try turning off app nap for VirtualBox. Command I or Get Info and check Prevent App Nap.

Thanks for the reply. I disabled app nap for VirtualBox as well as VirtualBoxVM.app Does this have anything to do with power nap? I don't have that enabled. Lets hope this helps.

So I thought this may have something to do with the display driver installed with guest additions. However, the problem has occurred while using the MS basic display driver.

I have tried switching in and out of fullscreen mode (with both the Oracle display driver for Win 8 as well as the MS basic display driver) after this has happened but it does not fix the issue. The screen stays black and I can't see anything on my VM. VB does pop up saying the color depth has been changed to 0-bit and that may not be optimal. I'd agree lol. It kind of looks like the display driver is crashing but I'm purely speculating.

Can you post a VBox.log as a compressed attachment when this thing occurs? It might give us a clue.

The log is attached. I didn't bother compressing as it isn't that big.