You can use the internal VM debug mode to troubleshoot internal virtual machines in instant-clone farms. With the internal VM debug mode, you can analyze failed internal virtual machines before these virtual machines are deleted. You must enable the internal VM debug mode before you create an instant-clone farm.
Procedure
- In the vSphere Web Client, select the master VM, and click .
The
Configuration Parameters window displays a list of parameter names and values.
- In the Configuration Parameters window, search for the cloneprep.debug.mode parameter.
If the master VM does not have the
cloneprep.debug.mode parameter, you must add
cloneprep.debug.mode as the parameter name and add a value of ON or OFF. If the master VM has the
cloneprep.debug.mode parameter, you can change the value of the parameter to ON or OFF.
- Enable or disable the internal VM debug mode for internal VMs.
- To enable the internal VM debug mode, set the value of cloneprep.debug.mode to ON. If you enable the internal VM debug mode, the internal VMs are not locked and cannot be deleted by Connection Server.
- To disable the internal VM debug mode, set the value of cloneprep.debug.mode to OFF. If you disable the internal VM debug mode, the internal VMs are locked and can be deleted by Connection Server.
For instant-clone actions such as prime, provision, resync, or unprime, the internal virtual machines use the value set in the master virtual machine. If you do not disable the internal VM debug mode, then the VMs remain in vSphere till you delete the VMs. For further debugging on instant-clone actions, you can also log in to the internal VM and view the instant-clone logs. You can also see the following VMware Knowledge Base articles for further debugging on instant-clone actions:
