Kernel Panic - Not Syncing - Failed Exception in Interrupt | Kali on ESXi

[saquibm6]

Hello,

I am getting the error "Kernel Panic - Not Syncing - Failed Exception in Interrupt" while I am trying to boot my VM (Kali) on Esxi 6.0

I had upgraded my ESXi from 5.5 to 6.0 after which I am getting this error. Since it's a hard Panic, I am unable to do anything.

If I try to run Live Linux OS or try to install a new OS (Debian 10 or Kali) on the already issued VM, it gives me "Kernel Panic - not syncing: Machine Halted" error

whereas

If I try to create a new virtual machine and then install an OS there or do Live boot in there, it gives me error "Kernel Panic - not syncing: Attempted to kill init! exit code=0x0000000b"

Can someone help me, any ideas on this whatsoever, I need all the help I can get. VMWare Logs have been attached from the VM.

Thanks in advance.

[tayfundeger]

Hi,

I want to make a little suggestion. Debian 10 is now supported with ESXi 6.5. Would you mind trying the same operations with ESXi 6.5?

VMware Compatibility Guide - Guest/Host Search

Thanks.

[saquibm6]

Thanks for the revert Tayfun, I will definitely try this and update.

In the meantime, I have a question. Since the VM was already working on 5.5, and does not on 6, and your suggestion is to update to 6.5 as the Debian 10 is supported in that version.

How is it that the same VM is supported on an older 5.5 version but not the newer 6.0 version and is now supported in 6.5 version? How is it that something that was already supported on an older version is not supported/working on a newer version?

Thanks & regards

[continuum]

I think the reason for the problem is the Debian VM inside ESXi VM inside unknown platform scenario.

It would help if you tell us the full story.

Other than that Kali should not be that picky about the guestOS version you configure - but as Kali runs tools like nmap and wireshark it may require promiscuos mode on the nics.

And that may require extra steps in a nested VM.

[tayfundeger]

The information contained in VMware HCL is written as a result of tests. Therefore, I do not know exactly why it is supported in the next version and why it is not supported in the previous versions.