OpenShift Local version 2.36 Error: end kernel panic - not syncing attempted to kill init exitcode=0x00007f00

[ashigro]

error starting OpenShift Local version 2.36 on Windows, crc VM shows error at boot: end kernel panic - not syncing attempted to kill init exitcode=0x00007f00

[anjannath]

@ashigro can you please use the issue template and provide information about your environment, that helps us in reproducing and properly addressing the issue

[ashigro]

General information

• OS: Windows
• Hypervisor: Hyper-V
• Did you run crc setup before starting it (Yes/No)? Yes
• Running CRC on: Desktop

CRC version

WARN A new version (2.36.0) has been published on https://developers.redhat.com/content-gateway/file/pub/openshift-v4/clients/crc/2.36.0/crc-windows-installer.zip
CRC version: 2.35.0+3956e8
OpenShift version: 4.15.10
Podman version: 4.4.4

CRC status

DEBU CRC version: 2.35.0+3956e8
DEBU OpenShift version: 4.15.10
DEBU Podman version: 4.4.4
DEBU Running 'crc status'
CRC VM:          Stopped
OpenShift:       Stopped (v4.15.10)
RAM Usage:       0B of 0B
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     81.25GB
Cache Directory: C:\Users\ashig\.crc\cache
DEBU Running '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" -Name ReleaseId).ReleaseId'
DEBU Running '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").EditionID'

CRC config

- consent-telemetry                     : yes

Host Operating System

OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19045 N/A Build 19045
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          N/A
Registered Organization:   N/A

Original Install Date:     3/8/2021, 11:42:33 PM
System Boot Time:          5/23/2024, 10:21:12 PM
System Manufacturer:       Gigabyte Technology Co., Ltd.
System Model:              To be filled by O.E.M.
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: AMD64 Family 16 Model 4 Stepping 3 AuthenticAMD ~3400 Mhz
BIOS Version:              American Megatrends Inc. FD, 1/23/2013
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi
Total Physical Memory:     16,364 MB
Available Physical Memory: 11,890 MB
Virtual Memory: Max Size:  18,796 MB
Virtual Memory: Available: 12,805 MB

Steps to reproduce

Expected

Actual

Logs

Before gather the logs try following if that fix your issue

$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue. Link to the log: https://gist.github.com/ashigro/56974598ee18f3b9c8cae261ef59caef

[ashigro]

@anjannath, thanks for quick response. I have shared the information above in Issue template. Let me know if you require any more information.

[anjannath]

@ashigro thanks for providing the details, i tried to reproduce it (on a intel machine) using crc version 2.35.0 and did not face this kernel panic issue, the differences are that i ran it on a intel machine with i7 10th gen and ram was 32gb, you are running on an AMD processor

can you try to create a VM directly in hyper-v using a rhel9 image and see if that works, you can download one for free from developer.redhat.com using a developer subscription

[ashigro]

I just tried with RHEL9 image, getting the same kernel panic error. It seems hardware doesn't support RHEL9.

[anjannath]

@ashigro could you please share the o/p of Get-CimInstance win32_Processor we might consider adding this to our docs if certain processors are not able to run crc/rhel9

in the meantime you can use the free dev-sandbox service to experiment with openshift, https://developers.redhat.com/developer-sandbox