VMWare Horizon View Instant Clone Errors during Proviosning

 

Horizon

Troubleshooting Instant Clones in the Internal VM Debug Mode

 Last Updated 09/01/2017  1

 Add To MyLibrary

< Ask New Question

You can use the internal VM debug mode to troubleshoot internal virtual machines in instant-clone desktop pools. 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 desktop pool.

Procedure

1. In the vSphere Web Client, select the master VM, and click Manage > Configure > VM Options > Edit > VM Options > Advanced > Edit Configuration.

   The Configuration Parameters window displays a list of parameter names and values.

2. 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.

3. 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 Horizon 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 Horizon Server.

   For instant clones 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.

 Instant Clones provisioning fails with the error: "Unable to prepare migration" (60397)

---

Last Updated: 12/19/2018Categories: Troubleshooting 1Language:                 Chinese (Simplified)JapaneseEnglish                          subscribe

 Symptoms

When creating a new Horizon Instant Clones pool or during Push Image/Maintenance operation on Horizon Instant Clones pool, you experience these symptoms:

• Some of the Horizon Instant Clones fail with the error:
  
  Unable to prepare migration. 
   
• This error is visible on vCenter Server tasks for all the clones that failed.

 Cause

This issue occurs because very rarely on vSphere 6.7, a cp-parent VM fails to quiesce properly. This causes "Unable to prepare migration" error when creating Horizon Instant Clones.

 Resolution

This is a known issue affecting VMware vSphere 6.7.x with Horizon 7.5 and later.

Currently, there is no resolution.

 Workaround

To work around this issue, follow either one of the workarounds:

Workarounds for on-prem Horizon deployment

Workaround #1 

Identify the cp-parent VM that is causing the failures by looking at the vCenter Server tasks. 

1. Navigate to the host on which this cp-parent VM resides. 
2. Set InstantClone.Maintenance attribute to value 1 in "Custom Attributes" on the the "Summary" page of the host. This deletes all the cp-parent VMs from the host, including the problem one. 
3. Once the cp-parent VMs are deleted, the host InstantClone.Maintenance will be set to 2. 
4. Edit the InstantClone.Maintenance attribute value to an empty string. 
5. Enable provisioning on the pool or recover the clones in error state.

Workaround #2

Identify the cp-parent VM that is causing the failures by looking at the vCenter Server tasks. 

1. Navigate to the host on which this cp-parent VM resides. 
2. Put the host into maintenance mode. This deletes all the cp-parent VMs from the host, including the problem one. The host will enter maintenance mode once all cp-parent VMs on it are deleted. 
3. Exit the host from maintenance mode. 
4. Enable provisioning on the pool or recover the clones in error state.

Workaround for Horizon instances on VMC

Identify the cp-parent VM that is causing the failures by looking at the vCenter Server tasks.

1. Navigate to the host on which this cp-parent VM resides.
2. Power off the cp-parent VM and delete it.
3. Enable provisioning on the pool or recover the clones in error state.

https://communities.vmware.com/thread/619413