2

I know my iso file is good because I've installed it on a few different laptops, but when I tried installing it in virtual box it freezes on this screen: frozen virtual box

This is my first time trying to set up a virtual machine. I followed this http://www.hacking-tutorial.com/hacking-tutorial/10-steps-how-to-create-kali-linux-virtual-machine-in-virtual-box/#sthash.FNC0pQz9.dpbs tutorial, except that I used my iso from before instead of kali whatever.

So far this is the most relevant previously asked question I've found on askubuntu.com, or elsewhere. But it seems to be about a previously installed OS.

Update: Maybe it's not frozen.. I've had it open for like an hour and it finally printed out a few more lines.. enter image description here

Community
  • 1
user273872
  • 233

3 Answers3

2

select that machine settings > system> processor then change number of processors to at least 2

Metoshi Nakamoto
  • 21
1

I've faced this issue, and after many trials, I remembered my BIOS did not have virtualization enabled. After I enabled this option in BIOS setup, everything is working fine. (Intel does not have an option for that)

SuperSluether
  • 975
Christiano dos Santos
  • 11
0

This panic screen — which you have not transcribed in full in your question but really should so that the text will be indexed and people will find it in the future — is the panic screen that results when process #1 exits after not handling signal #4 (illegal instruction).

As I just explained at https://askubuntu.com/a/706543/43344 , some of the important information has scrolled off your screen, namely the Comm: line that tells us what program was running as process #1. It could be Comm: sh, or Comm: init, or even Comm: run-init as in the AskUbuntu question that you linked to in your question.

You need to find out what was printed that has scrolled off the top of your screen. Without it, you cannot fully diagnose this problem beyond some unknown program did something unknown that caused an illegal instruction signal to be raised. Persuading the boot loader to switch the screen into, say, 50 line mode would be one way of doing this. Configuring VirtualBox with an appropriate serial device and bootstrapping with a serial console would be another.

The text that was printed later on is a red herring, by the way. That's just the interrupt-driven "entropy collection" in your kernel finally picking up enough "randomness". Your kernel is sitting spinning in an endless loop because of the panic.

Further reading

Community
  • 1
JdeBP
  • 3,979