Can't start Kali Linux in VirtualBox

[sysxprct]

Hi,

I am a beginner. It's the first time I've been using VirtualBox, and the first time I've been using Kali.
I've tried to install Kali Linux in VirtualBox.
I use Lubuntu 15.10 Wily.
The laptop has: 2 G RAM( 1243 MB for Kali ), Intel Core 2 Duo T5870 / 2 GHz

At the end of Installation, when Kali should start, has stopped


Loading, please wait...


After, I tried for a few times the next ones: change "quite" with "nomodset" or to delete "quiet" at all, and to start it in "recovery mode".

After few restarts of Kali, error in the console was:


"SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr"
Sorry, I don't have the print screen

Boot Kali Linux, press "space bar" and "e":

1.
Start Kali GNU/LInux without "quite" and with "nomodset" instead of "quite"
Print screens:1317 error:


5.389876 clocksource: tsc: mask: 0xfffffffffffffffffffff max_cycles: 0x35ae055c082 max_idle_ns xxxxxx ns


2.
Go to Advanced options for Kali GNU/Linux Kali GNU/Linux, with Linux 4.3.0-kali1-686-pae without "quite" and with "nomodset" instead of "quite" Print screens:1315 error:


for nomodset:

5.414774 hrtimer: interrupt took xxxxx ns


without "quite"


4.881669 clocksource: tsc: mask: 0xfffffffffffffffffffff max_cycles: 0x35adfce max_idle_ns xxxxxx ns


3.

Advanced options - recovery mode - without "quite" replace quite with "nomodset"
Print screens: 1318 error:


5.xxxx clocksource: tsc: mask: 0xfffffffffffffffffffff max_cycles: 0x35xxxxx max_idle_ns xxxxxx ns

INFO ABOUT HOST AND GUEST:


vboxmanage --version
5.0.14_Ubuntur105127

I couldn't find /var/log/vbox-install.log

Attached:
/var/log/Xorg.0.log
+
/home/sysprct/VirtualBox VMs/Kali Linux/Logs
1319


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily

Host & Guest - 32 bit

Amount of memory:
Total: 2048 MB
981 MB - Guest(Kali Linux)
1067 MB - Host

Any ideas please?
Thank you.

[Gh0sT.sh]

Turn off the option "Enable Nested Paging" in the VirtualBox configuration under Settings->System->Acceleration.

if didnt work boot Live cd and



Check module is being loaded
lsmod | grep i2c_piix4

If so, blacklist it in the file /etc/modprobe.d/blacklist.conf, by adding the following to the end of the file:
blacklist i2c_piix4

Update the initramfs
sudo update-initramfs -u -k all

[sysxprct]

Thank you for your advises Gh0sT.sh,


Turn off the option "Enable Nested Paging" in the VirtualBox configuration under Settings->System->Acceleration.

Acceleration Button is blocked, I can't access it at all, is gray color.


if didnt work boot Live cd and

1. I don't have the possibility to create a Live CD, tell me please, can I do something with a Live USB Stick?

2. Excuse me please but I am not so advanced, I it could work with the Live USB,?

3. I must create it from my main OS(Lubuntu) and it has to be a Live USB with Kali not with other Linux distro?

4. After, boot my PC from it at all, and use all the next 3 commands that you said in the console of the Live Kali USB ?



Check module is being loaded
lsmod | grep i2c_piix4

If so, blacklist it in the file /etc/modprobe.d/blacklist.conf, by adding the following to the end of the file:
blacklist i2c_piix4

Update the initramfs
sudo update-initramfs -u -k all





I've made a New Session(create a new OS) in Virtualbox:

A. When I tried to create "Live (686-pae)" Print screen: 1320
B. When I try to create "Live USB Persistence" Print screen: 1321


Thank you.

[duxim]

download an install VB on your computer
then download image you want to install from this page:
https://www.offensive-security.com/kali-linux-vmware-virtualbox-image-download/
check sh1sum when you finished your download
extract those 7z file. it is ovi file
then from VB go to File--->Import Appliance and navigate to extracted Kali ovi file
and just wait a little
on logon user is root, password is toor

and that is all

[bilyeti]

@sysxprct,
I had the same problem as you, but I have found a fix. You need to enable the Virtualization in the BIOS. But first you should check whether your chipset supports virtualization. I recommend checking out this link: http://www.sysprobs.com/disable-enable-virtualization-technology-bios