Storage VMotion fails with the error: Failed to unstun VM after disk reparent

Patch Fix

Pre-Patch Workaround

• isVMAffectedByKB1003874.pl checks if the virtual machine has a mis-matched CID value and therefore can be fixed with the next script. Copy this script to the Remote CLI host, into the location where you run svmotion.pl. For Windows Remote CLI installations, the default location is C:\Program Files\VMware\VMware VI Remote CLI\bin. For Linux Remote CLI installations, the default location is the home directory or /usr/sbin for the appliance.
   
• completeSVMForVMAffectedByKB1003874.pl fixes the CID issue on the virtual machine disk file. Run this script after checking if your system is affected, using the previous script. Copy this script to the service console of your ESX host in the /root directory.

To download these files:

1. Find the links to the scripts under the Attachments section at the bottom of this article.
2. Right-click each link and save the file to your machine.
   
   Note: If the host where you intalled the Remote CLI has a Web browser, you can save the files directly to that host. Then you need to copy only one file to another system (the ESX host).

Step 2: Verify Your Virtual Machine Is Affected

1. Open a Command Prompt window.
2. Change to the directory:
   
   cd "C:\Program Files\VMware\VMware VI Remote CLI\bin"
    
3. Run the command:
   
   isVMAffectedByKB1003874.pl

• You can also run this script as a precautionary measure on virtual machines that have not encountered this problem, before moving them with Storage VMotion.
• If the script indicates that the virtual machine is not affected by this issue, the next step does not fix the problem. You need to perform additional analysis and other troubleshooting steps with the help of documentation, the forum community, or Technical Support (if appropriate). For related information, see Snapshot Operations Submitted Directly to an ESX Server Host During Storage VMotion Corrupt Virtual Machine Data (1003114).

Step 3: Repair the Problem Virtual Machine

1. Log in to the service console of the ESX Server host where you copied the script.
    
2. Run the script completeSVMForVMAffectedByKB1003874.pl, specifying the name of the affected virtual machine as a command-line argument, surrounded by single quotes.
   
   For example:
   
   

   [root@esxhost root]# perl completeSVMForVMAffectedByKB1003874.pl 'Compact WinXP 2'
   
   The output looks similar to the following:
   
   Configuring your virtual machine to complete Storage VMotion...
   
   **************************** Success! ******************************
   The script has modified the VM so that it is able to complete the
   Storage VMotion, as described in KB 1003874.
   
   Please follow the rest of the steps in the KB to complete the
   Storage VMotion and power-on your VM.
   
   Do not attempt to Storage VMotion this VM again until you have
   installed patch bundle ESX350-200802411-BG.
   
   Original copies of all modified files have been placed in
   /vmfs/volumes/477e63a9-a760d731-eecc-000e0c819981/Compact WinXP 2_1/backups.
   ********************************************************************
   
   

3. Using VMware Infrastructure Client, create a snapshot of the virtual machine.
    
4. In the snapshot manager, select Delete All. This collapses the snapshot you just took with any remaining DMotion-* files on the source datastore into the disks on the target datastore.
    
5. Power on the virtual machine. This powers on the virtual machine using all the files on the target datastore, allowing the virtual machine to complete its migration.