Error: LCMVSPHERECONFIG1000022 Guest tools not running in Virtual Appliance during VCF Operations Deployment

Products

• VMware SDDC Manager / VCF Installer
• VCF Operations
• VMware Cloud Foundation

Issue/Introduction

VCF Operations cloud proxy deployment fails during the initial configuration phase in VMware Cloud Foundation 9.x. The VCF Installer reports that guest tools are not running, and the newly deployed virtual machine appears without an IP address or DNS configuration in vCenter. This article provides steps to re-trigger guest customization and resolve the deployment hang.

• VCF Installer fails with error: LCMVSPHERECONFIG1000022
• Message: Guest tools not running in Virtual Appliance. Provide required values and retry.
• The deployment logs show: com.vmware.vrealize.lcm.common.exception.vcenter.GuestToolsNotRunningException
• The Cloud Proxy VM is powered on in vCenter, but the IP Address, DNS, and VMware Tools status fields are blank.
• Opening the VM console shows a blinking cursor or an incomplete boot sequence.

Environment

• VCF 9.x

Cause

The Cloud Proxy virtual machine fails to execute the guest customization engine on the initial boot. This prevents the OS from applying the assigned networking (IP/DNS) and time synchronization settings. Without a valid network identity, the VMware Tools service fails to initialize, preventing the VCF Installer from verifying the node status.

Resolution

1. Log into the vCenter Server managing the management domain.
2. Locate the failed VCF Operations collector/cloud proxy node.
3. Perform a Reset or Power Cycle on the virtual machine.
4. Monitor the VM console. A reboot forces the guest customization engine to re-run and apply the OVF properties.
5. Verify the VM Summary tab in vCenter. Confirm the IP address and DNS fields are populated and VMware Tools status is Running.
6. Navigate back to the VCF Installer and click Retry.

Note: If the deployment subsequently fails with Error Code: LCMVROPSSYSTEM29002 Message: “Operations collector group operation failure – Wait timeout, Cloud Proxy node didn’t join the Operations cluster

Additional Information

To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.