[Bug]: my VM wont start up

[NEONBOX4444]

Version

trunk/main

Host OS Type

Windows

Host OS name + version

WINDOWS

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

ARM

Guest OS name + version

WINDOWS

Component

Unspecified

What happened?

My VM wont start due to a black screen
no log in screen no mouse no apps and nothing but a black screen

How can we reproduce this?

like this is what is going on basically

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.

[elbouazzatilouay-art]

i tried tiny 11 but lightweight before i did it it was fine after i did it it just shows that

[Forbidden0005]

same issue here

[JulianAtkins]

I've had this problem for 4-5 months. In my case, all Linux VMs work fine, but Win11 VMs open to a black screen and stop there.

I did find a workaround for this bug, I noticed that if I open my Linux VMs first, Win11 VMs do not work, but if I open the Win11 VMs first, then they do work!

Try the following:

1. boot the host into a clean state or stop all VMs on an existing host
2. all VMs must be stopped at this point
3. as root run systemctl restart vboxdrv
4. start Win11 VM
5. start other VMs

[alflr]

Without any VBox.log file we can't help any further here, unfortunately.

[JulianAtkins]

Without any VBox.log file we can't help any further here, unfortunately.

well, I would upload a VBox.log, but I know you'd reject it because I'm using the rpmfusion rpm packages instead of the official ones (like you've done in the past for other bugs I've opened). Maybe someone running the official thing can upload a log?

I just checked, the log has nothing relevant, the last few lines look like:

00:00:01.994805 EFI: VBoxDbg> unload 'IScsiDxe.efi' # 0xdd5da000 LB 0x1d100
00:00:01.995821 EFI: VBoxDbg> loadimage64 'VirtioNetDxe.efi' 0xdd656000 LB 0x4300
00:00:01.996687 EFI: VBoxDbg> loadimage64 'E1kNetDxe.efi' 0xdd777000 LB 0x2e60
00:00:01.997676 EFI: VBoxDbg> loadimage64 'UhciDxe.efi' 0xdd64c000 LB 0x4580
00:00:01.998577 EFI: VBoxDbg> loadimage64 'EhciDxe.efi' 0xdd647000 LB 0x4f00
00:00:01.999595 EFI: VBoxDbg> loadimage64 'XhciDxe.efi' 0xdd604000 LB 0x8660
00:00:02.000712 EFI: VBoxDbg> loadimage64 'UsbBusDxe.efi' 0xdd610000 LB 0x5260
00:00:02.001683 EFI: VBoxDbg> loadimage64 'UsbKbDxe.efi' 0xdd642000 LB 0x4020
00:00:02.002748 EFI: VBoxDbg> loadimage64 'UsbMassStorageDxe.efi' 0xdd5ff000 LB 0x4380
00:00:02.003613 EFI: VBoxDbg> loadimage64 'TcpDxe.efi' 0xdd5e5000 LB 0xce80
00:00:02.115215 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007fe028000000 w=1024 h=768 bpp=32 cbLine=0x1000 flags=0x0 origin=0,0
00:00:02.131923 xHCI: Hardware reset
00:00:02.134082 xHCI: USB Operational
00:00:02.215262 PS2K: Selected scan set 2
00:00:02.463756 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:06.821552 GUI: UIMediumEnumerator: Medium-enumeration finished!

and it just sits there in a black screen doing nothing, never showing the VirtualBox boot logo.

[alflr]

Yes, usually third party packages of VirtualBox are not supported, but it can't hurt to have the full VBox.log for reference here as well -- it might be that this still is a relevant issue we might want to have a peek at.

For instance, is Unattended Install enabled for this VM? Without a full VBox.log we can't do much here.