NSX Bare Metal Edge Deployment Fails Due to Kernel Panic

Products

• VMware NSX

Issue/Introduction

• Deployment of NSX bare metal edge is failing with Kernel Panic
• The installation completes successfully; however, the NSX bare metal edge server fails to boot and throws a kernel panic.
• The following kernel panic stack is observed during server boot
  
  15.771456] R11: autoslab_const_M_1pfc_P_drivers_scsi_lpfc_lpfc_init_8836_9_8836_9_S_76616_A_8_n_36+0x50f2/0x12b48 [slab obje
15.806758) R12: autoslab_size_M_lpfc_P_drivers_scsi_lpfc_lpfc_sli_16082_10_16082_10_S_1024_A_8_n_669+0x0/0x400 [slab object
15.819552] R15: autoslab_size_M_lpfc_P_drivers_scsi_lpfc_lpfc_sli_16082_10_16082_10_S_1024_A_8_n_669+0x58/0x400 [slab object
[ 15.8448271 FS: 0000000000000000 (0000) GS: ffff897c70200000(0000) kn1GS: 0000000000000000
[ 15.8570771 CS: 0010 DS: 0000 ES: 0000 CRO: 0000000080050033
[
15.869539) CR2: ffffffff823036a0 CR3: 0000000008464004 CR4: 0000000000760ef0 shadow CR4: 0000000000760ef0
15.880717] CR2: modprobe_path+0x0/0x100
[ 15.8920271 DRO: 0000000000000000 DR1: 000000000000000000 DRZ: 000000000000000000 [ 15.903944] DR3: 000000000000000000 DR6: 00000000fffe07f0 DR7: 00000000000000400
[ 15.9148601 PKRU: 55555554
[ 15.925844] ACID: 0003
[
15.937242] Kernel panic not syncing: grsec: halting the system due to suspicious kernel crash caused by root
  
  
• The server has an Emulex LPe35002-M2-D 2-Port 32Gb Fibre Channel adapter installed

Environment

VMware NSX

Resolution

This is a known issue caused by the Linux kernel and our NSX engineering team is aware of it. The issue will be resolved in the future version of NSX. 

Workaround:

To workaround the issue, disable the Emulex Fibre Channel adapter and boot the NSX bare metal edge server.