Hi, I've been using this VM (Virtualbox 6.1.18, ubuntu 64 bit) for a couple weeks now and it's been working fine. However, when i tried to start it up yesterday, the VM would just get stuck on a black screen with a single underscore.
I have tried to look through other forum posts with similar issues and have tried the following:
- Disable 3d acceleration (it wasn't on in the first place)
- Check if hyper-V is active (I couldn't find the lines "{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work..." in my log so I don't think this is the issue)
but nothing has helped so far, I have attached my last log and i hope someone could assist me.
Thank you.
Ubuntu VM black screen with single underscore on startup
-
Mathias1548
- Posts: 2
- Joined: 22. Feb 2021, 04:32
Ubuntu VM black screen with single underscore on startup
- Attachments
-
- VBox log.zip
- (60.1 KiB) Downloaded 7 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Ubuntu VM black screen with single underscore on startup
Well, you seem to have the RAM allocation side down pat. Now you only need to take care of the provision side!00:00:05.834919 Host RAM: 8080MB (7.8GB) total, 1259MB available
...
00:00:06.133738 RamSize <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)
00:00:06.134378 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
-
Mathias1548
- Posts: 2
- Joined: 22. Feb 2021, 04:32
Re: Ubuntu VM black screen with single underscore on startup
Ah, that makes sense. Sorry to bother with such a simple mistake.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Ubuntu VM black screen with single underscore on startup
FWIW it seems reasonable that an 8GB host should run a 2GB VM. It's just that you had lots of other stuff running that used up the available RAM before the VM was started. Easy thing to do...