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

VMware vSphere Virtual machine swapfiles are not deleted and left unused after HA failover (2035995)

  • 0 Ratings


  • Following a vSphere High Availability (HA) restart of virtual machines on another ESXi/ESX host, virtual machine swapfiles that were local to the failed ESXi/ESX host are left behind and remain unused.
  • Virtual machine swapfiles are not deleted and are left unused after HA failover.
  • Virtual machine swapfiles are not automatically cleaned up after HA failover when virtual machines are restarted on another ESXi/ESX host.


When a virtual machine is powered up on another host by a HA event, it is not able to access the previous swapfile if that swapfile location was local to the failed host. In this case, it creates a new swapfile. If the virtual machine is migrated back to the original host, afterwards it will not reuse the original swapfile.


This is a known issue affecting:
  • vSphere ESXi 4.1
  • vSphere ESXi 5.0
  • vSphere ESXi 5.1
  • vSphere ESXi 5.5
This issue is resolved in:
Currently, there is no resolution for:
  • vSphere ESXi 4.1
  • vSphere ESXi 5.0
To work around this issue:

After a HA host failure, manually delete virtual machine swapfiles from the local swapfile datastore which were left behind on the original (failed) ESXi/ESX host.

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