Black screen on VM start
-
- Posts: 7
- Joined: 6. Aug 2022, 07:02
Black screen on VM start
This seems to be happening for every VM I start on my ubunutu 22.04 machine. I am trying to run ubunutu 20.04 on virtualbox and continously get the black screen. virtualbox was working fine but started having this black screen since trying to use docker-compose inside of the vm and accidently shutting down the pc while downloading files.
I've confidently tried everything on the web but couldnt figure it out and tried reinstalling mulitple times.
the below is my error message.
I've confidently tried everything on the web but couldnt figure it out and tried reinstalling mulitple times.
the below is my error message.
- Attachments
-
- 22.04-2022-08-06-13-57-56.log
- (95.92 KiB) Downloaded 199 times
-
- 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 on VM start
Trying increasing graphics RAM to something substantially more than the current 16MB, i.e. max it out.
I'd given the VM a second CPU core too.
I'd given the VM a second CPU core too.
-
- Posts: 7
- Joined: 6. Aug 2022, 07:02
Re: Black screen on VM start
I've tried from 16MB ~ 128Mb maxing it out, and tried to increase my CPU core from 1~8. Still seemt o have the problem
-
- 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 on VM start
The suggestion was 2 cores, not any other number. With only 4 cores available no other number makes sense.
I need to see a new log containing these changes. Please zip the attachment this time.
I need to see a new log containing these changes. Please zip the attachment this time.
-
- Posts: 7
- Joined: 6. Aug 2022, 07:02
Re: Black screen on VM start
Thanks I've tried 2 cores and same issue so i have attached the log
- Attachments
-
- 22.04-2022-08-07-16-03-06.log
- (86.17 KiB) Downloaded 75 times
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Black screen on VM start
VirtualBox tries to determine the resolutions of your monitors, and screen 0 seems to give strange values. Can you tell us more about your monitors?22.04-2022-08-07-16-03-06.log wrote:00:00:01.307729 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 1994x27 x 3366x1413 00:00:01.376244 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 1 work area is actually resized to: 0x0 x 1920x1080
PS: During the last VM run, you didn't have enough free RAM on the host. But since this wasn't the case in the previous VM run, I don't think that it is important here.
-
- Posts: 7
- Joined: 6. Aug 2022, 07:02
Re: Black screen on VM start
Thank you. the laptop monitor is 15.6″ 1920×1080 FHD and external monitor is a 4k dell 27inch monitor. the VM does not work regardless of being connected to external monitor or not
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Black screen on VM start
I just noticed that you're using a 10 GB VDI, and I'd suspect that's not enough for a typical Ubuntu 22.04 installation. A disk full condition can lead to a blank screen also on physical PCs.
-
- Posts: 7
- Joined: 6. Aug 2022, 07:02
Re: Black screen on VM start
I've changed it to 40gb (was also previously 40gb but accidently put it as 10gb after reinstalling). no changes and same error :/
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Black screen on VM start
There's two steps to a disk size increase: please see How to Resize a Drive9907daniel wrote:I've changed it to 40gb ... no changes and same error :/
-
- Posts: 7
- Joined: 6. Aug 2022, 07:02
Re: Black screen on VM start
Ive created a new vm with same settings and 40gb disk size, yet I still get the error. The error happens continuously with blank screen even if i create new vms with larger disk sizze.
-
- Volunteer
- Posts: 843
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: Black screen on VM start
The latest vbox.log from the 'new' VM (completely shut down) showing all changes would be needed to help with identifying the problem.
Did you also check the issue of overcommitting RAM to the VM as mentioned by fth0 when you installed the new VM?
That Log showed:
Did you also check the issue of overcommitting RAM to the VM as mentioned by fth0 when you installed the new VM?
That Log showed:
but:00:00:01.264612 Host RAM: 15714MB (15.3GB) total, 5256MB (5.1GB) available
00:00:01.346552 RamSize <integer> = 0x00000002a0000000 (11 274 289 152, 10 752 MB, 10.5 GB)
-
- Posts: 7
- Joined: 6. Aug 2022, 07:02
Re: Black screen on VM start
yes I have.
pretty sure the main problem is in
ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
which recursively appears every 2seconds the vm runs infinitlu.
the updated log is as below.
pretty sure the main problem is in
ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
which recursively appears every 2seconds the vm runs infinitlu.
the updated log is as below.
- Attachments
-
- 20.04-2022-08-07-22-54-51.log
- (84.57 KiB) Downloaded 21 times
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Black screen on VM start
When being logged only once, this message is expected, but in your case, where it is logged continuously, it indicates a general problem indeed. But it cannot give any real clue to identify the cause. But I think I found your main problem anyway:9907daniel wrote:ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
QEMU/KVM is running on your host. Please make sure that QEMU/KVM is not running when you run a VirtualBox VM.