Kernel Panic when booting Metasploitable 2

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Cybermayhem
Posts: 1
Joined: 7. Sep 2022, 19:02

Kernel Panic when booting Metasploitable 2

Post by Cybermayhem »

My host is Windows 11, and my guest is Metasploitable (ubuntu-32bit)
I/O -APIC and PAE/NX is enabled
Error: Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot
ith apic=debug and send a report. Then try booting uith the 'noapic' option

From Logs HMR3Init: Attempting fall back to NEM: VT-x is not available, Do I need to make any vbox Settings change to make this VM Run. I reverted back to Vbox 6.1.36 from 6.1.38 along with the revelant Extension pack but still the same issue.
Error After changing processors to 2
Error After changing processors to 2
Kernel Panic.png (4.76 KiB) Viewed 12472 times
Metasploitable2-2022-09-07-22-32-43.rar
Logs
(15.4 KiB) Downloaded 225 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Kernel Panic when booting Metasploitable 2

Post by scottgus1 »

Aside from turning off host Hyper-V, see HMR3Init: Attempting fall back to NEM (Hyper-V is active), you could try the suggested grub boot option in Metasploitable's grub loader "noapic".
VM_Novice22
Posts: 1
Joined: 10. Sep 2022, 03:07
Primary OS: MS Windows other
VBox Version: PUEL
Guest OSses: Oracle 64-bit; Debian 64-bit

Re: Kernel Panic when booting Metasploitable 2

Post by VM_Novice22 »

I, too, was receiving the same errors on a similar configuration: Windows 11 host OS; VirtualBox 6.1.38; Metasploitable 2 on 64-bit Oracle Linux. Every time I wanted to boot the Metasploitable VM, I would have to hit "Esc" to enter the grub loader and type "noapic" then boot. Every. Single. Time. There had to be a better workaround.

After reviewing Chapter 8 of the VirtualBox Manual, I decided to try modifying the settings in CLI using VBoxManage. Using the latest version of PowerShell, I ran these two commands:
vboxmanage modifyvm <uuid|vmname> --acpi off
vboxmanage modifyvm <uuid|vmname> --ioapic off
(The uuid|vmname for me was "Metasploitable").
After running the PowerShell commands, I reopened the VirtualBox GUI, selected my "Metasploitable" VM, and clicked "Start." I did not encounter the errors anymore. Hopefully this helps!
brantcy
Posts: 1
Joined: 26. Nov 2022, 12:26

Re: Kernel Panic when booting Metasploitable 2

Post by brantcy »

VM_Novice22, I could kiss you!

Thank you so much for reminding me about using VBmoxManage to get rid of the need to change the ioapic setting every single time I loaded metasploitable2.

I have no idea how many hours you've saved me, but it would have definitely been a few! You rock!
Post Reply