Storage vmotion of VMs completes successfully, but VMs are still listing under old datastore.

Products

• VMware vSphere ESXi

Issue/Introduction

An administrator performing Storage VMotions, finds that they complete, but the VM(s) still show that they are using the datastore from which they migrated from.

Environment

vSphere (All versions)

ESXi (All versions)

Cause

Virtual machine configuration files (vmx file) located in the VM folder, contain all the details of the running VM, including the files it uses. When a Storage VMotion is performed, only these parts are moved with the VM, and anything left behind are essentially orphaned.

Another scenario where the datastore might still be referenced is if the VM is configured to use an ISO or serial port associated with that datastore, even if it's not currently connected. This setup can result in a reference to the original datastore.

Resolution

If an ISO is associated on the VM in this situation, the resolution is to remove/disconnect this on the VM settings.

Procedure:

• Right click subject VM and choose Edit Settings
  • On the Hardware tab, scroll down to you find the option for CD/DVD Media
    • If applicable, uncheck the "Connected" check box
  • Drop down the option for CD/DVD Media and change this to Client Device
  • Close edit settings for the changes to take effect

Note: In the case of a serial port, even after storage vMotion, it may still be connected to the original datastore. This must be changed manually by editing the VM settings > Serial Port > Browse > New Datastore.

Additional Information

VMs registered to old datastore with no data related to the virtual machines

Virtual Machine displays two datastores in Summary tab despite all its files being located on one datastore