Fresh 2.4 installation from ISO : kernel panic - not syncing: attempted to kill init exitcode 0x00007f00

[sirtcp]

Version

2.4.50

Installation Method

Security Onion ISO image

Description

installation

Installation Type

Standalone

Location

on-prem with Internet access

Hardware Specs

Exceeds minimum requirements

CPU

4

RAM

25GB

Storage for /

100

Storage for /nsm

200

Network Traffic Collection

tap

Network Traffic Speeds

Less than 1Gbps

Status

No, one or more services are failed (please provide detail below)

Salt Status

No, there are no failures

Logs

No, there are no additional clues

Detail

Hi,

I've been using 2.3 for the last few months on Proxmox VE, and it has been working perfectly. I love the product. However, I want to upgrade to 2.4. The problem is, upon boot, I encounter a kernel panic error. I've tried both versions 2.4.50 and 2.4.40, and I've verified the signatures as well. However, during the initial boot after choosing Grub, none of the options I've tried on both versions seem to move forward. Instead, they end up with the following error: "kernel panic - not syncing: attempted to kill init exitcode 0x00007f00." Unfortunately, I can't see the complete error because the Proxmox boot resolution is very small.

Regards,
Yousuf

Guidelines

• I have read the discussion guidelines at Read before posting! #1720 and assert that I have followed the guidelines.

[cm-ops]

Is your VM CPU set to host? https://docs.securityonion.net/en/2.4/proxmox.html#cpu

[sirtcp]

Thank you, I missed this part. now it's working Thank you for the update. Regards, Yousuf

…

On Wed, Mar 6, 2024 at 2:05 AM Chris Morgret ***@***.***> wrote: Is your VM CPU set to host? https://docs.securityonion.net/en/2.4/proxmox.html#cpu — Reply to this email directly, view it on GitHub <#12496 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABV5OHTS44T7JY4DWSUKW2DYWYXQFAVCNFSM6AAAAABEHEPDZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DMOBVGU2DK> . You are receiving this because you authored the thread.Message ID: <Security-Onion-Solutions/securityonion/repo-discussions/12496/comments/8685545 @github.com>