Search the VMware Knowledge Base (KB)
View by Article ID

ESXi host running DLR VM fails with a purple diagnostic screen (2149132)

  • 0 Ratings


  • VMware ESXi host fails with a purple diagnostic screen in NSX for vSphere 6.2.2 and later environments
  • You may see backtrace similar to:

    2017-02-13T16:32:10.376Z cpu3:35986)@BlueScreen: #DF Exception 8 IP 0x418028fc1488 SP 0x439164913000
    2017-02-13T16:32:10.376Z cpu3:35986)Code start: 0x418028000000 VMK uptime: 6:03:32:26.326
    2017-02-13T16:32:10.376Z cpu3:35986)0x439164913000:[0x418028fc1488]VdrFLEntryFind@<None>#<None>+0xe4 stack: 0x0
    2017-02-13T16:32:10.377Z cpu3:35986)0x439164913020:[0x418028fc2cd7]VdrRoutePkt@<None>#<None>+0x19f stack: 0x0
    2017-02-13T16:32:10.377Z cpu3:35986)0x439164913150:[0x418028fc4894]VdrEtherInput@<None>#<None>+0x53c stack: 0x0
    2017-02-13T16:32:10.377Z cpu3:35986)0x439164913290:[0x418028fb98f7]VdrProcessPackets@<None>#<None>+0x12b stack: 0x0
    2017-02-13T16:32:10.378Z cpu3:35986)0x4391649134c0:[0x41802814e981]IOChain_Resume@vmkernel#nover+0x1f9 stack: 0x430303a93f98
    2017-02-13T16:32:10.378Z cpu3:35986)0x439164913560:[0x41802813226e]PortOutput@vmkernel#nover+0xae stack: 0x430303968c70
    2017-02-13T16:32:10.378Z cpu3:35986)0x4391649135a0:[0x4180281dd022]vmk_PortOutput@vmkernel#nover+0x56 stack: 0x4391649136df
    2017-02-13T16:32:10.379Z cpu3:35986)0x4391649135e0:[0x418028fb95fa]VdrTxToVswitch@<None>#<None>+0x1b2 stack: 0x0

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


This issue occurs under the following circumstances:

  • A DLR Control VM is configured for both routing and bridging.
  • An original LIF IP on the DLR is edited and changed to another IP address. 
  • The original LIF IP address is configured and in use on another device in the environment.
When a LIF IP is edited, the ESXi host incorrectly retains a record of the original IP to DLR MAC address mapping.
When network traffic to that IP is received on the host, the ESXi is not able to route the packet correctly due to the incorrect internal MAC entry and this results in a purple diagnostic screen. This purple diagnostic screen affects the ESXi host which is running the DLR Control VM.

In an environment configured with vSphere High Availability, if the DLR Control VM is restarted by HA on another ESXi server, this host may also experience a purple diagnostic screen.

Note: The purple diagnostic screen may not happen in an environment where DLR does not have bridging enabled. However, network communication will fail to the VM that is using the original IP which was configured on the DLR LIF.


This is a known issue affecting VMware NSX for vSphere 6.3.x.

This issue is resolved in VMware NSX for vSphere 6.2.7, available at VMware Downloads.

To avoid this issue, delete and recreate the DLR LIF if there is a need to change the IP address on a routed/bridged DLR LIF.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

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.


  • 0 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)

Please enter the Captcha code before clicking Submit.
  • 0 Ratings