virtualbox.org

As you can see by the title, every time i try to boot the Debian 8.x Kali Linux (Whatever it's called) Guest on Virtual Box, I get this error on the step: "Install the System".
This error has been very annoying and I have been looking through the depths of YouTube and google, but no solution. Any help at this point is greatly appreciated as I have been working on this problem for over 14 hours.

Note:
I have enabled all Virtualization Technologies for my Dell Optiplex 780 System
I have installed the USB 2.0 extension pack for my VB system.
My virtual disk for Kali Linux is 22 GB and 1 GB of RAM

Again I am greatly stressed and any help on this matter is appreciated.

Thank you for this help.

Any other steps I can take while you assess the log file?

00:00:03.675442 Host RAM: 3965MB (3.8GB) total, 1445MB available
00:00:06.568464 RamSize  <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)
00:00:06.568916 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

1024 MB seems too little for the 64-bit Kali, but then again you can't afford too much more, otherwise your host is going to starve. What you could do is to assign 2048 MB, but you've got to quit/kill all other user processes on your host, like browsers with multiple tabs (they're the worst memory hogs). On the other hand you could afford a couple of MB more for your graphics. Take it up to 32 or 64 MB.

00:00:07.440967 Full Name: "Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz"

You don't have a really strong CPU. Core2 Duo is a quite old technology and it might be the one that's causing the problems. BTW, congratulations for assigning only one out of the two available CPUs to your guest.

After that I see that you pause and resume the VM several times. I really don't know why.

And finally, see if updating VirtualBox to 5.1.26 might help you...

Thanks for the help, I appreciate alot.

Updraded VB, gave more ram (2048), added another processor total of two, and closed all programs while running it. Still did not work. I am getting a new desktop soon in a couple of days so I will try again then