Virtual machines (VMs) migrated via Storage vMotion may continue to display an association with the source datastore in the inventory. This prevents administrators from unmounting or decommissioning the legacy storage because vCenter Server identifies active registrations. This behavior is common in environments utilizing linked clones, instant clones, or VMs with persistent snapshots. Symptoms include the old datastore appearing in the Related Objects tab, the VM Summary tab, or errors when attempting to delete the source LUN. Identifying and clearing these persistent disk descriptor references is required to release the storage lock.
In VDI and snapshot-heavy environments, VMs often run on delta disks (snapshots). While Storage vMotion relocates the active delta files, the disk's descriptor file may contain a hard-coded path to a parent base disk or a shared replica residing on the old datastore. vCenter maintains the registration link to preserve the integrity of the snapshot chain. Additionally, peripheral device configurations (ISO mappings or serial port logs) can hold active references to the source storage.
[!CAUTION] VDI Warning: Do not use the standard vCenter Consolidate or Delete All Snapshots options for managed VDI clones (linked/instant clones). Performing these actions manually can orphan the VM or corrupt the desktop broker database. Use the VDI management console for remediation.
Recompose or Update the VDI Pool (VDI Environments)
Verify and Disconnect ISO Media
Perform Snapshot Consolidation (Non-VDI VMs)
Redirect Serial Port Backing Files