Information regarding specifying or manually moving the ESXi host for vCLS deployment
Article ID: 431796
Updated On:
Products
Issue/Introduction
This article provides information on whether it is possible to manually move a vCLS instance to a specific ESXi host, prevent it from running on a specific host, and explains its resource usage impact on other virtual machines.
Environment
VMware vSphere 8.0 Update 3 and later
Cause
The embedded vCLS architecture introduced in vSphere 8 Update 3 uses a CRX container runtime instead of traditional virtual machines. This architecture is designed to be fully automated and managed entirely by vSphere to ensure cluster availability. Because it is a system-managed process, user interventions such as affinity rules or manual placements are not supported by design.
Resolution
It is not possible to manually specify a destination ESXi host, manually move vCLS, or permanently prevent vCLS from running on a specific host. There is no built-in function to control the placement of embedded vCLS agents, as the system automatically handles their lifecycle and distribution across the cluster.
Regarding resource consumption, the embedded vCLS is highly optimized. Each agent consumes minimal resources, specifically 1 vCPU and 160 MB of memory. Since it operates as a lightweight process entirely in memory without relying on shared storage, it does not negatively impact the performance of other virtual machines under normal operation.
Additional Information
Feedback
