VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Cloned virtual machines might show Error state after a transient failure

Details

After a reset, recompose, refresh, or rebalance due to a transient failure of networks, datastores, services, or the View server, cloned virtual machines change the state to Error from Ready state.
If such a cloned virtual machine in Error state is auto-provisioned and is not assigned to a user, the View administrator can delete it.
If the cloned virtual machines are assigned to a user or cannot be deleted for a certain reason, you can change its state to Ready. Refer the Solution section to change the state.

Solution

To change the state of a cloned virtual machine in Error state to Ready state:
  • Reset the cloned virtual machine: Resetting a cloned virtual machine does not erase the modifications in the OS disk of the virtual machine. So, reset the virtual machine if the Error was caused by customization failure in the previous power-on attempt.
  • Refresh the cloned virtual machine: Refreshing (recompose or rebalance) a cloned virtual machine restores the OS disk to its initial state. All user updates in the OS disk are erased. So, refresh the virtual machine if the Error was caused by a previous provisioining failure.

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: 1007820
  • Updated: Aug 31, 2009
  • Products:
    VMware View Manager
  • Product Versions:
    VMware View Manager 3.x