[SOLVED] Kali Linux (32-bit software virtualization) Error; Kernel Panic During Install or Live Boot Through VirtualBox

daver12345 · 01-07-2018, 11:33 PM

Hello all.

When booting Kali Linux in VirtualBox through Live Boot or Install, I get a kernel panic error that I can do nothing about. I have a fully updated kernel and kernel-headers, but nothing seems to be working. I would really appreciate all the help I can get.

Thanks.

Error: https://imgur.com/a/a5ADq

Hopefully one of you can help.

jsbjsb001 · 01-07-2018, 11:46 PM

Quote:

Originally Posted by daver12345

Hello all.

When booting Kali Linux in VirtualBox through Live Boot or Install, I get a kernel panic error that I can do nothing about. I have a fully updated kernel and kernel-headers, but nothing seems to be working. I would really appreciate all the help I can get.

Thanks.

Error: https://imgur.com/a/a5ADq

Hopefully one of you can help.

https://www.linuxquestions.org/quest...ad-4175614092/
https://docs.kali.org/introduction/s...use-kali-linux

!!! · 01-08-2018, 12:08 AM

Hello. Some general troubleshooting ideas:

Basically, more info needed to troubleshoot, similar to what a 'bug report' requires, tho this is likely a 'procedural' issue.

Try acpi=off or try this:

Quote:

Go to your virtual machine -> Settings -> System
Then change Chipset from PIIX3 to ICH9 and enable "Enable IO APIC"

Does this happen if you do the same [make] "a fully updated kernel &headers"
using Debian (or Ubuntu), and similarly ?make an updated kernel? ?
More info on exactly how you "updated kernel" needed (to verify valid procedure; have you done this before? [experience level?])

Googling this: panic "fatal exception in interrupt" updated kernel solved
may provide ideas on how to narrow this down, and areas to look into
(to provide details necessary to troubleshoot).

Possibly some of the stack traceback (routine names) and especially the 'RIP/EIP' where the panic occurred, may provide clues (when added to Google keywords).

Best wishes. p.s. there is also a 'sticky' on kernel panic (tho possibly not directly related, it may have useful ideas).

Added: I'm confused by your Thread Title:

Quote:

Kali Linux (32-bit software virtualization) Error; Kernel Panic During Install or Live Boot Through VirtualBox

"panic during install or booting .iso" (my interpretation) seems to contradict "built a kernel" Also, what OS in the VBox 'host'? (and why '32bit'?)

daver12345 · 01-08-2018, 07:39 PM

Quote:

Originally Posted by !!!

Added: I'm confused by your Thread Title:"panic during install or booting .iso" (my interpretation) seems to contradict "built a kernel" Also, what OS in the VBox 'host'? (and why '32bit'?)

Sorry about the contradiction, this is my first time posting on Linux Questions and I’m trying to get used to how I should word things. The VBox host is Fedora 27 and it’s 32bit because apparently software virtualization doesn’t support 64bit. (My computer doesn’t support hardware virtualization.)

jsbjsb001 · 01-08-2018, 08:15 PM

Quote:

Originally Posted by daver12345

Sorry about the contradiction, this is my first time posting on Linux Questions and I’m trying to get used to how I should word things. The VBox host is Fedora 27 and it’s 32bit because apparently software virtualization doesn’t support 64bit. (My computer doesn’t support hardware virtualization.)

If you cannot get Kali working in a VM; how do you expect your going to be able to use it for it's intended purposes? (which is hacking - as stated below)

I suggest you read both the second link in my signature as well as the following:

Quote:

Originally Posted by Kali's own developers

What’s Different About Kali Linux?

Kali Linux is specifically geared to meet the requirements of professional penetration testing and security auditing. To achieve this, several core changes have been implemented in Kali Linux which reflect these needs:

Single user, root access by design: Due to the nature of security audits, Kali Linux is designed to be used in a “single, root user” scenario. Many of the tools used in penetration testing require escalated privileges, and while it’s generally sound policy to only enable root privileges when necessary, in the use cases that Kali Linux is aimed at, this approach would be a burden.

Network services disabled by default: Kali Linux contains systemd hooks that disable network services by default. These hooks allow us to install various services on Kali Linux, while ensuring that our distribution remains secure by default, no matter what packages are installed. Additional services such as Bluetooth are also blacklisted by default.

Custom Linux kernel: Kali Linux uses an upstream kernel, patched for wireless injection.
A minimal and trusted set of repositories: given the aims and goals of Kali Linux, maintaining the integrity of the system as a whole is absolutely key. With that goal in mind, the set of upstream software sources which Kali uses is kept to an absolute minimum. Many new Kali users are tempted to add additional repositories to their sources.list, but doing so runs a very serious risk of breaking your Kali Linux installation.

Is Kali Linux Right For You?

As the distribution’s developers, you might expect us to recommend that everyone should be using Kali Linux. The fact of the matter is, however, that Kali is a Linux distribution specifically geared towards professional penetration testers and security specialists, and given its unique nature, it is NOT a recommended distribution if you’re unfamiliar with Linux or are looking for a general-purpose Linux desktop distribution for development, web design, gaming, etc.

Even for experienced Linux users, Kali can pose some challenges. Although Kali is an open source project, it’s not a wide-open source project, for reasons of security. The development team is small and trusted, packages in the repositories are signed both by the individual committer and the team, and — importantly — the set of upstream repositories from which updates and new packages are drawn is very small. Adding repositories to your software sources which have not been tested by the Kali Linux development team is a good way to cause problems on your system.

While Kali Linux is architected to be highly customizable, don’t expect to be able to add random unrelated packages and repositories that are “out of band” of the regular Kali software sources and have it Just Work. In particular, there is absolutely no support whatsoever for the apt-add-repository command, LaunchPad, or PPAs. Trying to install Steam on your Kali Linux desktop is an experiment that will not end well. Even getting a package as mainstream as NodeJS onto a Kali Linux installation can take a little extra effort and tinkering.

If you are unfamiliar with Linux generally, if you do not have at least a basic level of competence in administering a system, if you are looking for a Linux distribution to use as a learning tool to get to know your way around Linux, or if you want a distro that you can use as a general purpose desktop installation, Kali Linux is probably not what you are looking for.

In addition, misuse of security and penetration testing tools within a network, particularly without specific authorization, may cause irreparable damage and result in significant consequences, personal and/or legal. “Not understanding what you were doing” is not going to work as an excuse.

However, if you’re a professional penetration tester or are studying penetration testing with a goal of becoming a certified professional, there’s no better toolkit — at any price — than Kali Linux.

If you are looking for a Linux distribution to learn the basics of Linux and need a good starting point, Kali Linux is not the ideal distribution for you. You may want to begin with Ubuntu, Mint, or Debian instead. If you’re interested in getting hands-on with the internals of Linux, take a look the “Linux From Scratch” project.

ondoho · 01-09-2018, 01:46 AM

Quote:

Originally Posted by daver12345

The VBox host is Fedora 27 and it’s 32bit because apparently software virtualization doesn’t support 64bit. (My computer doesn’t support hardware virtualization.)

ok.
obviously you should use a 32bit kali iso.
it should still work, but you won't be happy running a graphical desktop. or maybe not even able to.
have you tried booting anything in virtualbox?

!!! · 01-09-2018, 04:41 AM

Interesting... So the 'updated kernel' is Fedora27 (host), not Kali (guest).

Attached you can see that I reproduced your panic!!! (XP host)
For me, without the boot option vga=0 (to 6, so not vesa), the defaults just hang (black screen, 100% cpu).
I don't know why. I'd suggest submitting a bug report to Kali. (or VBox.org; see min-req)
(I also don't understand the syslinux 'three dashes'.)

Can you tell us more about your CPU? 64bit (or 32bit?), withOUT VT-x?

Maybe try the mini 36MB .iso I used; Did you try the boot options I suggested?
It seems to use syslinux, so hit tab (instead of grub's e).

Yes, "does any Linux .iso boot"? Try my favorite here: http://minimal.linux-bg.org/download...017_32-bit.iso
It's only 7MB, so I thus see 'no excuses' for not trying it & letting us know (that it boots ok)!!!

Spend at least fair portion an hour reading thru the Google results of these exact search:
panic "fatal exception in interrupt" solved
panic "fatal exception in interrupt" solved "32 bit" virtualbox|vmware|kvm|xen|qemu
and I think you may find some ideas/clues (maybe to better search keywords).

Let us know what you find (future www-searchers may be helped by your info)

I'm guessing this isn't related to 'kali' (unless their particular kernel .config has something that causes this). Or maybe it's syslinux (doubtful; Idk, sorry)

daver12345 · 01-09-2018, 07:39 AM

Quote:

Originally Posted by ondoho

ok.
obviously you should use a 32bit kali iso.
it should still work, but you won't be happy running a graphical desktop. or maybe not even able to.
have you tried booting anything in virtualbox?

I am using a 32bit ISO. Other than Kali, no. I’ve contemplated trying another Linux install to see if it works.

daver12345 · 01-09-2018, 07:41 AM

!!! I’ll try the mini ISO later. When you reproduced the panic, did you find a way to fix it, or not at all?

jsbjsb001 · 01-12-2018, 04:43 AM

Quote:

Originally Posted by daver12345

...I’ve contemplated trying another Linux install to see if it works.

I'd strongly suggest you take your own advice there.

WFV · 01-14-2018, 07:14 PM

i was unable to get Kali32 to install in VirtualBox on a Win10pro64 host with same error after many attempts and different Kali 32 bit iso's so gave up and installed the 64 bit version instead without issue - if you're doing it to learn Kali, the 64 bit version gives you everything for that purpose - the reason for recommending Kali 32 for vocational pen testing is that 32 bit will get into both 32 & 64 bit machines that the 64 bit can't always pen 32bit machines, or at least that is what my instructor from barracuda says... otherwise, i'm not fluent in Kali

daver12345 · 01-17-2018, 10:02 AM

I seemed to get it working with other linux distributions and macOS, so I guess Kali doesn’t like my computer/VirtualBox.

Bravius · 05-12-2019, 09:49 AM

Quote:

Originally Posted by daver12345

Hello all.

When booting Kali Linux in VirtualBox through Live Boot or Install, I get a kernel panic error that I can do nothing about. I have a fully updated kernel and kernel-headers, but nothing seems to be working. I would really appreciate all the help I can get.

Thanks.

Error: https://imgur.com/a/a5ADq

Hopefully one of you can help.

Please can you also help me since U have got the same problem with my Kali Linux

Vermithrax · 05-14-2019, 12:12 PM

Bear on mind that newer VirtualBox releases (>=6._) don't support 32bit hosts anymore. I was stuck for some time trying to figure out why the system won't even boot and why the hell kernel panicked. And then I saw that VB is ditching the oldtimers.
P. S. VB 5.2 works like a charm.

hydrurga · 05-14-2019, 03:45 PM

Quote:

Originally Posted by Vermithrax

Bear on mind that newer VirtualBox releases (>=6._) don't support 32bit hosts anymore. I was stuck for some time trying to figure out why the system won't even boot and why the hell kernel panicked. And then I saw that VB is ditching the oldtimers.
P. S. VB 5.2 works like a charm.

Thanks for the heads-up - I was unaware of that.

VirtualBox's home page says that support for 5.2 will last until July 2020.