EnsNetWorld PSOD crash occurs on ESX host prepared for NSX Enhanced Data Path
search cancel

EnsNetWorld PSOD crash occurs on ESX host prepared for NSX Enhanced Data Path

book

Article ID: 445836

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware NSX

Issue/Introduction

  • ESX host crashes with a Purple Screen of Death (PSOD)

    <DATE>T11:49:15.721Z cpu4:2101965)@BlueScreen: #PF Exception 14 in world 2101965:EnsNetWorld- IP 0x42002e341321 addr 0x18
    PTEs:0x12e74d027;0x8144624007;0x0;
    <DATE>T11:49:15.721Z cpu4:2101965)Code start: 0x42002be00000 VMK uptime: 24:16:40:36.359
    <DATE>T11:49:15.722Z cpu4:2101965)0x4539ed4dbc10:[0x42002e341321]rte_port_uplink_writer_tx_bulk@(nsxt-ens-25318226)#<None>+0x375 stack: 0x404040404010000
    <DATE>T11:49:15.722Z cpu4:2101965)0x4539ed4dbd10:[0x42002e3927c1]EnsProcessOutPortsIntr@(nsxt-ens-25318226)#<None>+0x2c6 stack: 0x0
    <DATE>T11:49:15.723Z cpu4:2101965)0x4539ed4dbde0:[0x42002e3b1158]Ens_NetWorldRun@(nsxt-ens-25318226)#<None>+0xc9 stack: 0x0
    <DATE>T11:49:15.723Z cpu4:2101965)0x4539ed4dbf30:[0x42002e3c9b02]EnsNetWorldCallback@(nsxt-ens-25318226)#<None>+0x29b stack: 0x450181eed000
    <DATE>T11:49:15.723Z cpu4:2101965)0x4539ed4dbf90:[0x42002c07d001]vmkWorldFunc@vmkernel#nover+0x46 stack: 0x42002e3c9868
    <DATE>T11:49:15.724Z cpu4:2101965)0x4539ed4dbfe0:[0x42002be23eef]CpuSched_StartWorld@vmkernel#nover+0xe8 stack: 0x0
    <DATE>T11:49:15.724Z cpu4:2101965)0x4539ed4dc000:[0x42002c00cb67]Debug_IsInitialized@vmkernel#nover+0x10 stack: 0x0

  • The ESX host is prepared for NSX, Enhanced Data Path(EDP) which is the default for VCF 9 environments
  • There are one or more VMs in the environment configured with an e1000 network driver

Environment

VMware NSX 4.x, 9.x

Cause

The crash results from an error in handling packets from VMs configured with an e1000 driver. This issue is specific to the combination of ESX hosts prepared for Enhanced Data Path running VM(s) configured with e1000 network adapter.

Resolution

This is a known issue impacting VMware NSX.

Identify any VMs configured with an e1000 vNIC and convert them to vmxnet3

  1. In the vSphere Client, right click on the VM and select Edit Settings
  2. Click the 3 dots beside the network adapter and select Remove device


  3. Click OK to save
  4. Right click on the VM and select Edit Settings
  5. Click ADD NEW DEVICE > Network Adapter
  6. Configure the network and select vmxnet3 adapter



  7. Click OK to save

 

Alternatively if there is a requirement to run a VM with e1000, TSO must be disabled within that VM.