This is a known issue. Currently, there is no resolution.
To work around this issue and display the vswp datastore in the virtual machine summary tab, enable vswp datastore display in the vSphere Client and Web. Shut down and restart the affected virtual machine to recreate the vswp file.
To ensure the vswp file is configured to enable its creation on the correct datastore, open the virtual machine’s vmx file and verify the vswp file path.
To open the virtual machine’s vmx file and verify the vswp file path:
- Open an SSH session to the ESXi host, hosting the affected virtual machine.
- Change directory to the virtual machine's directory on the datastore:
cd /vmfs/volumes/datastoreName/vmDirectoryName
- Open the virtual machine's vmx file in less:
less vmName.vmx
- Locate the line entry starting with:
sched.swap.derivedName =
- This line displays the location where the vswp file was created. For example:
sched.swap.derivedName = "/vmfs/volumes/526980a3-e7b0d522-1ccb-00505617367d/testVM/testVM-12269531.vswp"