Kali freezes when being turned on.

[CauseImGod]

So I have installed kali linux on my virtual box. Installation went great no crashes, no nothing, but when i try to start my kali already installed it just freezes and hangs until i turn it off. What to do Guys?!?

[mpack]

Post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[CauseImGod]

Here you go

[Perryg]

00:00:01.784119 Host RAM: 4095MB total, 1625MB available
00:00:02.359905 RamSize <integer> = 0x0000000075100000 (1 963 982 848, 1 873 MB)

First problem is RAM over commitment. You are assigning more memory than is available.

00:00:13.505621 Changing the VM state from 'SUSPENDED' to 'POWERING_OFF'

This shows you shut it off at just over 13 seconds. Hardly enough time given the memory issue.

[CauseImGod]

00:00:01.784119 Host RAM: 4095MB total, 1625MB available
00:00:02.359905 RamSize <integer> = 0x0000000075100000 (1 963 982 848, 1 873 MB)

First problem is RAM over commitment. You are assigning more memory than is available.

00:00:13.505621 Changing the VM state from 'SUSPENDED' to 'POWERING_OFF'

This shows you shut it off at just over 13 seconds. Hardly enough time given the memory issue.

Well i went less on Rams and started program and left it for like 20 minutes. It keeps being frozen. I would post an image but i cant xd

[Perryg]

It would be nice if you posted the new log.

[CauseImGod]

It would be nice if you posted the new log.

i left it for aprox. 1h still no results or changes

[Perryg]

00:00:04.583851 Host RAM: 4095MB total, 586MB available
00:00:06.243833 RamSize <integer> = 0x000000005bc00000 (1 539 309 568, 1 468 MB)

And it will never start until you free up some memory on the host. You can see this by looking at the top part of the log, so until you can produce a log that shows you have ample available memory to support a guest, there is not need in replying.

[CauseImGod]

00:00:04.583851 Host RAM: 4095MB total, 586MB available
00:00:06.243833 RamSize <integer> = 0x000000005bc00000 (1 539 309 568, 1 468 MB)

And it will never start until you free up some memory on the host. You can see this by looking at the top part of the log, so until you can produce a log that shows you have ample available memory to support a guest, there is not need in replying.

now im more than sure i did everything right but still no changes. It's supposed to aleast write some lines and it doesnt even do that.

[CauseImGod]

It hangs like this

[mpack]

You probably still have memory overcommitment. The rule of thumb is that you can use 50% of available host RAM for the VM. It should not be marginal. Either add more RAM to your host, or get used to shutting stuff down if you want to run this VM, or give the VM substantially less RAM e.g. 512MB.

I'm also concerned at the small amount of display RAM you're giving the VM: 14MB is a very small VRAM allocation, this alone could affect performance.