Running Hyper-Converged Infrastructure (HCI) in a nested virtualization environment can be quite complex and might not always work as expected due to limitations and compatibility issues. Nested virtualization involves running a hypervisor inside another hypervisor, which can introduce various complications.

The configuration you described involves aCloud running inside ESXi, which is itself a virtualized environment. Then, within aCloud, you've configured virtual disks (vmdk) to emulate SSDs using SATA controllers.

HCI solutions typically require direct access to hardware resources for optimal performance and stability. Nested virtualization might not provide the necessary access or stability for HCI solutions to function correctly. The health check failures you're encountering might be due to the nested virtualization setup and the limitations it imposes.

For HCI deployments, especially for production or critical environments, it's generally recommended to use bare-metal installations to ensure proper access to hardware resources, performance, and stability. Running HCI on bare metal eliminates many of the potential issues that arise from nested virtualization.

If you're exploring HCI in a testing or non-production environment, nested virtualization might be used for experimentation or learning purposes. However, it's crucial to be aware that it might not fully replicate the behavior or performance of a bare-metal HCI deployment.

If possible, consider deploying HCI on dedicated physical hardware to ensure optimal performance and stability, especially if you encounter issues with nested virtualization that hinder proper functioning of the HCI solution.

Running Hyper-Converged Infrastructure (HCI) in a nested virtualization environment can be quite complex and might not always work as expected due to limitations and compatibility issues. Nested virtualization involves running a hypervisor inside another hypervisor, which can introduce various complications.

The configuration you described involves aCloud running inside ESXi, which is itself a virtualized environment. Then, within aCloud, you've configured virtual disks (vmdk) to emulate SSDs using SATA controllers.

HCI solutions typically require direct access to hardware resources for optimal performance and stability. Nested virtualization might not provide the necessary access or stability for HCI solutions to function correctly. The health check failures you're encountering might be due to the nested virtualization setup and the limitations it imposes.

For HCI deployments, especially for production or critical environments, it's generally recommended to use bare-metal installations to ensure proper access to hardware resources, performance, and stability. Running HCI on bare metal eliminates many of the potential issues that arise from nested virtualization.

If you're exploring HCI in a testing or non-production environment, nested virtualization might be used for experimentation or learning purposes. However, it's crucial to be aware that it might not fully replicate the behavior or performance of a bare-metal HCI deployment.

If possible, consider deploying HCI on dedicated physical hardware to ensure optimal performance and stability, especially if you encounter issues with nested virtualization that hinder proper functioning of the HCI solution.