Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

ESXi 5.1 host stops responding and displays a purple diagnostic screen when NetFlow monitoring is enabled on a dvPortGroup (2042370)

Symptoms

  • After upgrading to ESXi 5.1, one or more ESXi hosts randomly stop responding
  • ESXi hosts fail with a purple diagnostic screen
  • You see a backtrace similar to: 
2012-12-12T03:17:29.779Z cpu8:42450)Panic: 766: Panic from another CPU (cpu 8, world 42450): ip=0x41801d47b266:
#GP Exception 13 in world 42450:vmm0:Datacen @ 0x41801d4b7aaf
2012-12-12T03:17:29.779Z cpu8:42450)Backtrace for current CPU #8, worldID=42450, ebp=0x41221749b390
2012-12-12T03:17:29.780Z cpu8:42450)0x41221749b390:[0x41801d4b7aaf]vmk_SPLock@vmkernel#nover+0x12 stack: 0x41221749b3f0, 0xe00000000000
2012-12-12T03:17:29.780Z cpu8:42450)0x41221749b4a0:[0x41801db01409]IpfixFilterPacket@<None>#<None>+0x7e8 stack: 0x4100102205c0, 0x1, 0x
2012-12-12T03:17:29.781Z cpu8:42450)0x41221749b4e0:[0x41801db01f36]IpfixFilter@<None>#<None>+0x41 stack: 0x41801db01458, 0x4100101a2e58
2012-12-12T03:17:29.781Z cpu8:42450)0x41221749b580:[0x41801d53cf40]IOChain_Resume@vmkernel#nover+0x247 stack: 0x4100101bcf80, 0x412404e
2012-12-12T03:17:29.781Z cpu8:42450)0x41221749b5d0:[0x41801d52c154]PortOutput@vmkernel#nover+0xe3 stack: 0x4100101a2940, 0x41221749b730
2012-12-12T03:17:29.782Z cpu8:42450)0x41221749b630:[0x41801da3776f]EtherswitchForwardLeafPortsQuick@<None>#<None>+0xd6 stack: 0x41801d5
2012-12-12T03:17:29.782Z cpu8:42450)0x41221749b830:[0x41801da38fd8]EtherswitchPortDispatch@<None>#<None>+0x13bb stack: 0x412400000017,
2012-12-12T03:17:29.783Z cpu8:42450)0x41221749b8a0:[0x41801d52b337]Port_InputResume@vmkernel#nover+0x146 stack: 0x410010174858, 0x41801
2012-12-12T03:17:29.783Z cpu8:42450)0x41221749b8f0:[0x41801d51aa30]Net_AcceptRxList@vmkernel#nover+0x157 stack: 0x4100101712c0, 0x1, 0x
2012-12-12T03:17:29.783Z cpu8:42450)0x41221749b950:[0x41801d5a7751]NetPollWorldletCallback@vmkernel#nover+0x5c stack: 0x0, 0x0, 0x41221
2012-12-12T03:17:29.784Z cpu8:42450)0x41221749bad0:[0x41801d50af2b]WorldletProcessQueue@vmkernel#nover+0x486 stack: 0x41221749bb10, 0xb
2012-12-12T03:17:29.784Z cpu8:42450)0x41221749bb10:[0x41801d50b5a5]WorldletBHHandler@vmkernel#nover+0x60 stack: 0x10000000000003a, 0x41
2012-12-12T03:17:29.785Z cpu8:42450)0x41221749bb90:[0x41801d4207fa]BH_Check@vmkernel#nover+0x185 stack: 0x100000006, 0x418042000180, 0x
2012-12-12T03:17:29.785Z cpu8:42450)0x41221749bbd0:[0x41801d44be55]IDT_IntrHandler@vmkernel#nover+0x1fc stack: 0x41221749bce8, 0x41801d
2012-12-12T03:17:29.785Z cpu8:42450)0x41221749bbe0:[0x41801d510064]gate_entry@vmkernel#nover+0x63 stack: 0x0, 0x0, 0x0, 0x0, 0x0
2012-12-12T03:17:29.786Z cpu8:42450)0x41221749bce8:[0x41801d6dbd6f]Power_HaltPCPU@vmkernel#nover+0x276 stack: 0x41221749bde8, 0x4122174
2012-12-12T03:17:29.786Z cpu8:42450)0x41221749bde8:[0x41801d5bd114]CpuSchedIdleLoopInt@vmkernel#nover+0x873 stack: 0x410007930088, 0x41
2012-12-12T03:17:29.787Z cpu8:42450)0x41221749bed8:[0x41801d5c4bef]CpuSchedDispatch@vmkernel#nover+0xabe stack: 0x0, 0x0, 0x0, 0x410051
2012-12-12T03:17:29.787Z cpu8:42450)0x41221749bf48:[0x41801d5c5f1f]CpuSchedWait@vmkernel#nover+0x242 stack: 0x410000000000, 0x418000000
2012-12-12T03:17:29.788Z cpu8:42450)0x41221749bf98:[0x41801d5c6140]CpuSched_VcpuHalt@vmkernel#nover+0x14b stack: 0x41801d5b84f9, 0x4100
2012-12-12T03:17:29.788Z cpu8:42450)0x41221749bfe8:[0x41801d4f3698]VMMVMKCall_Call@vmkernel#nover+0x1af stack: 0x0, 0x0, 0x0, 0x0, 0x0
2012-12-12T03:17:29.788Z cpu8:42450)0x41801d4c77d8:[0xfffffffffc223a12]__vmk_versionInfo_str@esx#nover+0xde3224b1 stack: 0x0, 0x0, 0x0,
2012-12-12T03:17:29.788Z cpu8:42450)Panic: 872: Halting PCPU 8. 

Resolution

VMware is aware of this issue and is currently working to resolve this in a future release.
 
To work around this issue, you can disable NetFlow monitoring on all the dvSwitches and Portgroups in vCenter Server.
 
To disable NetFlow monitoring:
  1. In the vSphere Client, navigate to Home > Inventory > Networking.
  2. For every dvSwitch:

    1. Click each dvPortGroup & dvUplinksGroup.
    2. Click Edit Settings > Monitoring.
    3. Change the NetFlow status setting to Disabled.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 3 Ratings
Actions
KB: