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

NSX Manager high CPU utilization triggered by many simultaneous vMotion tasks (2150668)

  • 0 Ratings
Language Editions


  • NSX Manager high CPU triggered by many simultaneous vMotion tasks.
  • DFW is configured with dynamic security groups which have criteria based on VM name or VM guest OS.


When a VM is vmotioned, destination host send two updates for these properties:

  • VM.guestFullName
  • VM.guestHostName
  • First update has these values empty. This causes VM to be removed from dynamic criteria security group.
  • Second update sends correct value again. This causes VM to be added again to dynamic criteria security group.
  • This causes dynamic criteria security group evaluation to be triggered twice, with no change in the result.


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

Note: This is a known issue affecting VMware NSX for vSphere 6.2.7 and earlier and 6.3.x.

To work around this issue if you do not want to upgrade, do not use dynamic security group based on VM name or VM guest OS.

Additional Information

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

See Also

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