We are having Horizon 7.9 running on ESX 6.7 build 16075168, with Windows 10 1903 desktops and NVIDIA M60 cards. We are planning to switch from Linked Clones to Instant Clones, but looks like Instant Clones are not 'instant' when GPU is used.
We see that the Instant Clones go through an additional reboot cycle upon 'delete on logoff'. When the user logs off, the machine is deleted, a new machine is provisioned, but it comes without the nVIDIA GPU attached. Then the VM is shutdown and comes back with attached GPU. This delay defeats the purpose of Instant Clones.
Anybody knows if this is a known issue and when it will be resolved?
Not sure if we experience the same delay but you could configure some reserve desktops in your desktop pool to counter the setup time.
The initial rollout of a desktop pool indeed takes some time, because of the creation of the cp-replica, cp-template and cp-parent.
Here is a very cool video from VMware which covers the instant clone provisioning: How Horizon Instant clone provisioning works - YouTube
That's just a workaround, but not a solution to the problem.
Yea, I'm well aware of the instant clone lifecycle, but this looks like a bug.
Yea, I saw that and added a comment as well. But I don't think we have a solution yet. I am thinking of raising an SR.