Search the VMware Knowledge Base (KB)
View by Article ID

Virtual Machine on RDM Shared Storage Becomes Invalid After Migration from ESX Server 2.5x to ESX Server 3.5 or ESX Server 3i (1003092)

  • 7 Ratings


When you migrate a virtual machine that resides on RDM shared storage from an ESX Server 2.5.x host to an ESX Server 3 version 3.5 or an ESX Server 3i version 3.5 host, the virtual machine is in an invalid state after migration. The virtual machine is listed as "Invalid" in the VirtualCenter inventory.
Consider the following scenario:
  1. Create a virtual machine on RDM storage attached to an ESX Server 2.5.4 host that is managed by a VirtualCenter Server version 1.4.

  2. Upgrade the VirtualCenter Server to version 2.5.

  3. Add an ESX Server 3i host to the VirtualCenter inventory.

  4. Make the VMFS-2 LUN attached to the ESX Server 2.5 host available to the ESX Server 3i host.

  5. Power off the virtual machine on the ESX Server 2.5 host.

  6. Migrate the virtual machine from the ESX Server 2.5 host to the ESX Server 3i host, keeping the .vmdk file on the same VMFS volume.

  7. Put the ESX Server 3i host into maintenance mode and perform a VMFS Upgrade operation.

The virtual machine is now invalid, and its status in the VI Client is shown as Invalid.


You can remove the virtual machine from the VirtualCenter inventory and create a new virtual machine. When you create the new virtual machine, make sure you map to the correct RDM. As an alternative, contact VMware Customer Support.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 7 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? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 7 Ratings