Opened 6 years ago
Last modified 6 years ago
#17761 new defect
Virtual machine stuck at initializing (windows logo)
| Reported by: | Leviathan | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.12 |
| Keywords: | stuck, boot | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
-Create a windows 10 32 bits virtual machine -2 GB of hard disk + ISO Image (SATA) -128 MB graphics -4 GB of dedicated TAM
Attachments (2)
Change History (4)
by , 6 years ago
by , 6 years ago
| Attachment: | VBoxHardening.log added |
|---|
Another log. I am not sure if this one is neccessary
comment:1 by , 6 years ago
Replying to Leviathan:
-Create a windows 10 32 bits virtual machine -2 GB of hard disk + ISO Image (SATA) -128 MB graphics -4 GB of dedicated TAM
Sorry, I meant RAM, not TAM.
comment:2 by , 6 years ago
VirtualBox VM 5.2.6 r120293 win.amd64 (Jan 15 2018 14:58:38) release log
You should upgrade to the latest version of VirtualBox, 5.2.12 as of this writing.
00:00:09.175230 Host RAM: 8104MB (7.9GB) total, 3898MB (3.8GB) available 00:00:09.937450 RamSize <integer> = 0x00000000da000000 (3 657 433 088, 3 488 MB, 3.4 GB)
You're allocating RAM for your guest, that is close to the available RAM on your host. Lower the RAM to your guest at 2048 MB. It's more than enough for a 32-bit Win10 installation.
00:00:17.272563 GUI: 2D video acceleration is disabled 00:00:09.938665 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
2D/3D acceleration is disabled. Shutdown the VM and enable them in the VM settings » Display. You'll also notice that the max VRAM will jump from 128 to 256 MB after that; max the VRAM as well. Then re-install the Guest Additions (GAs) in the guest.
00:00:09.939391 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes 00:00:13.257171 Full Name: "Intel(R) Pentium(R) CPU N3710 @ 1.60GHz"
And that's your main problem. You will need to address/fix this. Your Pentium N3710 most certainly supports VT-x, so it's a matter of enabling it in the BIOS. See your PC's manufacturer help on how to do this. Also, make sure that nothing else has an exclusive hold on the VT-x.
Finally, may I suggest something? It's usually better and faster, if issues get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".
Log of the issue