Vm Guide

When I hit install on the VM a black box appeared and said "This kernel requires an x86-64 CPU, but only detected an i686 CPU.
Unable to boot - please use a kernel appropriate for your CPU. What do I do?


You can use a 32 bit Kali iso and it should work. It appears you have downloaded a 64 bit Kali iso. You will need 4 things to get 64 bit Kali to work on a host machine. (1)
 64 bit hardware (2) 64 bit operating system on host machine. (3)
hardware virtualization on motherboard. and (4) hardware virtualization
enable in BIOS.


It would probably help if you had a minimum of 20GB storage on the hard drive. Kali has bumped up their storage requirements since I made the video. I've added some notes about this in the description and an annotation in the video. The reason for going up to 20GB is if you wish to add additional programs to your Kali virtual guest.

####################################################
NtCreateFile(\Device\VBoxDrvSub) failed 0x0000034
STATUS_OBJECTIF_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping?starting. Try 'sc.exe query vboxdrv' to get more information about it state. Rebooting may actual help. (rc=101)

Make sure the kernel module has been loaded successfully
####################################################

I would try installing without using a network mirror. You're the second person who pointed this out so a network mirror is probably down. After installing Kali you should be able to get all the latest upgrades by using "sudo apt-get update" and "sudo ap-get upgrade" from the command line.

If this is VirtualBox version 4.3.14 there may be a problem with your windows antivirus. I would try going up to version 4.3.20- so far

"apt-get". Try separating the commands on at the &&. && is used to put more than one command on a single line. It is not needed if you put each command on a separate line.

actual file name is VBoxLinuxAdditions.run with a capital B. in VBox. Linux is case sensitive. Make sure you have copied the file correctly and make sure you have changed the permissions on the VBoxLinuxAdditions.run file.