PSOD: #PF Exception 14 in world #######:tq:qlnativef IP 0x########## addr 0x8
search cancel

PSOD: #PF Exception 14 in world #######:tq:qlnativef IP 0x########## addr 0x8

book

Article ID: 370549

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • ESXi Host crashed with PSOD
  • Issue in qlnativefc driver 
  • Message seen is similar to:
    @BlueScreen: #PF Exception 14 in world #######:tq:qlnativef IP 0x########## addr 0x8
    YYYY-MM-DDTHH:MM:SS.671Z cpu73:2098070)0x1234:[0x1234]qlnativefcTimer@(qlnativefc)#<None>+0x0 stack: 0x0, 0x0, 0x0, 0x0, 0x0
    YYYY-MM-DDTHH:MM:SS.671Z cpu73:2098070)0x1234:[0x1234]VmkTimerQueueWorldFunc@vmkernel#nover+0x0 stack: 0x0, 0x0, 0x0, 0x0, 0x0
    YYYY-MM-DDTHH:MM:SS.671Z cpu73:2098070)0x1234:[0x1234]CpuSched_StartWorld@vmkernel#nover+0x0 stack: 0x0, 0x0, 0x0, 0x0, 0x0
    YYYY-MM-DDTHH:MM:SS.671Z cpu73:2098070)0x1234:[0x1234]Debug_IsInitialized@vmkernel#nover+0x0 stack: 0x0, 0x0, 0x0, 0x0, 0x0

Environment

7.x
8.x

Cause

The issue is related to a specific module called "VMID" in the vmhba's qlnativefc driver.  It is enabled by default starting in the qlnativefc driver version 5.3.81.2.

Resolution

This issue has been fixed in qlnativefc driver 5.4.84.0 version and above

Note: Before updating the qlnativefc driver to 5.4.84.0, verify the ESXi version as the driver is compatible with ESXi version that is 8.0 U3 and above. 

 

Workaround:

Before executing the workaround, read the following documentation to determine if the VMID feature can be disabled in the environment.

 

1. Put the host into maintenance mode.

2. SSH to the ESXi host and run the following command to get current module status:

esxcfg-module -g qlnativefc

 

Expected output:

qlnativefc enabled = 1 options = ''

3. Run the following command to disable VMID on the adapter:

esxcfg-module -s "ql2xvmidsupport=0" qlnativefc

4. Run the following command to see if the changes have been made

esxcfg-module -g qlnativefc

 

Expected output:

qlnativefc enabled = 1 options = 'ql2xvmidsupport=0'

5. Reboot the ESXi host.

6. Run the command again to ensure that the module has been disabled:

esxcfg-module -g qlnativefc