VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

In certain configurations, Storage VMotion fails and the virtual disk or RDM is destroyed

Symptoms

  • Storage VMotion (SVMotion) fails during migration
  • Cannot perform a Storage VMotion 
  • The virtual disk or RDM is destroyed
  • You receive the error:

    Source detected that destination failed to resume.

  • Virtual machine fails to resume from the original configuration and you receive the errors:
    • Cannot open the disk
    • Reason: Device or resource busy

Resolution

This issue only occurs under the following conditions:
  • You perform a Storage VMotion of a virtual machine with at least 2 disks
  • 1 RDM is located in the same directory as the .vmx file
  • The virtual disk or RDM is located in the target VMFS volume
  • The RDM or the virtual disk on the source volume and the RDM or virtual disk on the target volume have the same name.
The result of the this configuration is that the RDM or virtual disk on the target is overwritten with the content of the file from the source volume.
 
To avoid this issue:
  1. Identify which virtual machines meet the above conditions.
  2. Power off each virtual machine
  3. Rename the virtual disk or RDM on the source OR the target volume using the commands:

    # cd /vmfs/volumes/<volume>/<directory-containing-the-vmdk-file>
    # vmkfstools –E <old-filename>.vmdk <new-filename>.vmdk

  4. Edit the .vmx file and change the virtual disk or RDM name to the newly renamed one.
  5. Power on the virtual machine.

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (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? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 1015183
  • Updated: Oct 27, 2009
  • Products:
    VMware ESX
  • Product Versions:
    VMware ESX 3.5.x