Debian guest black screen

Discussions related to using VirtualBox on Windows hosts.
Post Reply
MangoLinux
Posts: 2
Joined: 19. Jul 2019, 16:08

Debian guest black screen

Post by MangoLinux »

I am running Vbox 6.0.10 on Windows 10 and I have a Debian guest that boots up to a black screen but while it boots up the screen changes from full screen to small screen several times.
Attachments
VBox-log-2019-07-19-10-03-23.zip
(27.44 KiB) Downloaded 17 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: Debian guest black screen

Post by mpack »

00:00:02.742566 Host RAM: 8076MB (7.8GB) total, 2767MB (2.7GB) available
...
00:00:03.258316 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:03.258605 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
I'm surprised the VM boots at all with this gross resource conflict. Free up host RAM, and you'll need to drastically reduce that guest RAM assignment.
MangoLinux
Posts: 2
Joined: 19. Jul 2019, 16:08

Re: Debian guest black screen

Post by MangoLinux »

I freed up as much memory as I can and reduced the guest RAm to 512MB issue is the same. new log updated. This was working on Monday
Attachments
VBox-Log-2019-07-19-11-34-07.zip
(25.71 KiB) Downloaded 19 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Debian guest black screen

Post by socratis »

MangoLinux wrote:and reduced the guest RAm to 512MB
00:00:00.382482 Host RAM: 8076MB (7.8GB) total, 4809MB (4.6GB) available
Maybe you've gone a little bit overboard. You can definitely afford now 1.5 or 2 GB.
MangoLinux wrote:This was working on Monday
What happened on Tuesday and later?
00:00:01.255662 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)
Increase that to 32, 64 or even max it out at 128 MB.
00:00:00.328215 VirtualBox VM 6.0.10 r132072 win.amd64 (Jul 12 2019 09:34:54) release log
00:00:16.503044 VMMDev: Guest Additions information report: Version 5.2.22 r126460 '5.2.22'
You should attend to this as soon as you get your "vision" back...
00:00:01.577098 AIOMgr: C:\Users\123917\VirtualBox VMs\parrot-security\parrot-security-disk002.vmdk
Why is there only a disk002.vmdk there? Was there a disk001.vmdk?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply