Black Screen CentOS 7, Virtual Box 5.2

Discussions about using Linux guests in VirtualBox.
Post Reply
joseluisbz
Posts: 57
Joined: 26. Jan 2017, 19:18
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows, macOS, CentOS

Black Screen CentOS 7, Virtual Box 5.2

Post by joseluisbz »

Hi,

Virtual Box 5.2
I was working with my guest (centOS 7), Host macOS Sierra 10.12.6, I changet to another application in my host, when I returned to CentOS 7, I get Black Screen with blinking cursor.

I tried sending Signal (Ctrl + Alt + Del) to get ask me to do, but The Screen remains black.

I don't know what happens.

Here the log.
Attachments
VBox.log.zip
Log with Events for black Screen on CentOS 7
(18.52 KiB) Downloaded 14 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Black Screen CentOS 7, Virtual Box 5.2

Post by mpack »

I'm not seeing a description of what you did next, i.e. so you shut down the guest and started it again and ... ?

I do see this in the log...
VBox.log wrote: 00:12:22.816257 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
00:12:22.816267 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
00:12:22.816281 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
00:12:22.838985 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=0 h=0 bpp=0 cbLine=0x0 flags=0x0
00:12:22.839063 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
00:12:22.839199 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
00:12:22.839212 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
00:12:22.839231 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Using fallback buffer since no source bitmap is provided
00:12:23.565281 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:12:23.565374 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:12:23.565461 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:12:23.565475 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:12:23.565482 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
00:12:23.577450 xHCI: USB Suspended
00:12:23.677880 HDA: Disabled DMA position buffer
00:12:23.677927 HDA: Codec reset
00:12:23.677949 HDA: Reset
00:19:02.884063 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 47x23 x 1393x877
00:19:05.158431 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 49x23 x 1391x877
00:19:59.865795 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 49x0 x 1391x900
00:20:19.418066 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 49x23 x 1391x877
00:20:21.380253 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 49x0 x 1391x900
I'm seeing a lot of display size changes (the above is just an excerpt), going on for than 10 minutes. What were you doing during that time? I then see that peculiar size change (first highlighted section) to a display size of 0x0 with no display buffer. Possibly this is just the start of a display driver reset, since it then seems to follow normal sequence you see on bootup. However the second highlighted section shows that it didn't work.

I would suggest starting the guest OS in safe mode (or whatever CentOS gives you as an equivalent), and I'd bring the VirtualBox Guest Additions up to something more recent than 5.1.10 (which is what you have at present).

I also see a warning in the log about audio stalls being likely. I don't really think you should do anything about this yet, just be aware of it.
Post Reply