Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
ESXi 6.0 host fails with PSOD error:NOT_IMPLEMENTED bora/vmkernel/filesystems/devfs/devfs.c:2655 In the vmkernel.log file, you will see messages similar to:YYYY-MM-DDT16:08:08.632Z cpu21:937436)cr0=0x8001003d cr2=0x3a34d0000 cr3=0xbd2c3000 cr4=0x216cYYYY-MM-DDT16:08:08.633Z cpu21:937436)@BlueScreen: NOT_IMPLEMENTED bora/vmkernel/filesystems/devfs/devfs.c:2655YYYY-MM-DDT16:08:08.633Z cpu21:937436)Code start: 0x418035e00000 VMK uptime: 13:11:53:23.734YYYY-MM-DDT16:08:08.633Z cpu21:937436)0x43936ee1b360:[0x418035e780da]PanicvPanicInt@vmkernel#nover+0x37e stack: 0x43936ee1b3f8YYYY-MM-DDT16:08:08.634Z cpu21:937436)0x43936ee1b3f0:[0x418035e783f5]Panic_NoSaveNoReturn@vmkernel#nover+0x4d stack: 0x43936ee1b450YYYY-MM-DDT16:08:08.634Z cpu21:937436)0x43936ee1b450:[0x418035e56974]Int6_UD2Assert@vmkernel#nover+0x12c stack: 0x4180361a8509YYYY-MM-DDT16:08:08.634Z cpu21:937436)0x43936ee1b4f0:[0x418035ec8044]gate_entry_@vmkernel#nover+0x0 stack: 0x0YYYY-MM-DDT16:08:08.634Z cpu21:937436)0x43936ee1b5b0:[0x418036096efe]DevFS_AddDynamicDeviceWithAttributes@vmkernel#nover+0x23e stack: 0x4YYYY-MM-DDT16:08:08.635Z cpu21:937436)0x43936ee1b630:[0x41803609f540]FSDisk_RegisterDevice@vmkernel#nover+0x54 stack: 0x430300000000YYYY-MM-DDT16:08:08.635Z cpu21:937436)0x43936ee1b670:[0x4180360a9622]SCSIRegisterDeviceWithDevFS@vmkernel#nover+0xc2 stack: 0x2e38303a383YYYY-MM-DDT16:08:08.635Z cpu21:937436)0x43936ee1b8b0:[0x4180360a9842]SCSIExportLogicalDevice@vmkernel#nover+0x32 stack: 0x0YYYY-MM-DDT16:08:08.636Z cpu21:937436)0x43936ee1b8d0:[0x4180360ae30b]vmk_ScsiRegisterDevice@vmkernel#nover+0x88b stack: 0x20000078YYYY-MM-DDT16:08:08.636Z cpu21:937436)0x43936ee1bab0:[0x4180367c5be0]nmp_RegisterDevice@com.vmware.vmkapi#v2_3_0_0+0x7c stack: 0x43054bd3YYYY-MM-DDT16:08:08.636Z cpu21:937436)0x43936ee1bb00:[0x4180367bfca4]nmpPathClaimEnd@com.vmware.vmkapi#v2_3_0_0+0x210 stack: 0x43035696a6YYYY-MM-DDT16:08:08.637Z cpu21:937436)0x43936ee1bb70:[0x4180360d2575]SCSIMPClaimruleRunSync@vmkernel#nover+0x5f9 stack: 0xfffffffffffffffYYYY-MM-DDT16:08:08.637Z cpu21:937436)0x43936ee1bd30:[0x4180360e4016]SCSIScanTargets@vmkernel#nover+0x12e stack: 0x9e4cb40c0812YYYY-MM-DDT16:08:08.637Z cpu21:937436)0x43936ee1bf10:[0x4180360e44e0]SCSIScanOneAdapter@vmkernel#nover+0xd4 stack: 0x430356e20fc0YYYY-MM-DDT16:08:08.638Z cpu21:937436)0x43936ee1bf30:[0x418035e5057e]helpFunc@vmkernel#nover+0x3c2 stack: 0x0YYYY-MM-DDT16:08:08.638Z cpu21:937436)0x43936ee1bfd0:[0x418036016bfe]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0YYYY-MM-DDT16:08:08.643Z cpu21:937436)base fs=0x0 gs=0x418045400000 Kgs=0x0
This issue occurs because devfs heap is full.
Reboot is required for settings to take effect.
This is a known issue affecting ESXi 6.0.Currently, there is no resolution.To work around this issue, increase the value of storageMaxDevices to 1024.To increase the value using vSphere Client, go to Software > Advanced settings > VMKernel > vmkernel.boot.StorageMaxDevices.
ESXi ホストで障害が発生して次のパープル スクリーン エラーが表示される：「NOT_IMPLEMENTED bora/vmkernel/filesystems/devfs/devfs.c:2655」ESXi 主机发生故障并显示紫色屏幕错误：“NOT_IMPLEMENTED bora/vmkernel/filesystems/devfs/devfs.c:2655”