VxRail: Virtual machine creation may fail because agent is unable to retrieve VM creation options from the host
Summary: Virtual machine creation may fail because agent is unable to retrieve VM creation options from the host. This occurs when an administrator is unable to connect directly to the ESXi host or manage under vCenter server. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
vCenter Server displays the error:
Virtual machine creation may fail because agent is unable to retrieve VM creation options from the host.
Warning: If LACP is configured on the vSAN network, do not restart management agents on ESXi hosts running vSAN.
- Restarting the management agents may impact any tasks that are running on the ESXi host at the time of the restart.
- Check for any storage issues before restarting the Host
daemon hostdservice orservices.sh.
Cause
The agents or services on the ESXi host may have halted.
Resolution
To resolve this issue use one of the following procedures:
1. Restart the Management agents on the ESXi host using Direct Console User Interface (DCUI);
- Connect to the console of your ESXi host.
- Press F2 to customize the system.
- Log in as root.
- Use the Up and Down arrows to go to Troubleshooting Options and then select Restart Management Agents.
- Press Enter.
- Press F11 to restart the services.
- When the service restarts, press Enter.
- Press Esc to log out.
Note: You can also restart services using the Host Client. In Host Client, select Host, then Manage, then Services, and then select the service to restart.
2. Restart Management agents in ESXi Using ESXi Shell or SSH:
- Log in to ESXi Shell or SSH as root. For Enabling ESXi Shell or SSH, see Using ESXi Shell in ESXi 6.x, 7.x and 8.x (2004746)
.
- Restart the ESXi host daemon and vCenter Agent services using these commands:
/etc/init.d/hostd restart /etc/init.d/vpxa restart
Caution:
- If LACP is enabled and configured, do not restart management services using the
services.shcommand. Instead, restart independent services using the/etc/init.d/module restartcommand. - If the issue is not resolved, and you are restarting all the services that are a part of the
services.shscript, take a downtime before proceeding to the script. - If NSX is configured in the environment, do not run the
/sbin/services.sh restartcommand because this restarts all services on the ESXi host. - If you must restart the management agents on the ESXi host, restart
vpxa,host.d, andfdmindividually. - If you must also run the
/sbin/services.sh restartcommand because restarting each management agent does not work, then migrate all the VMs off the ESXi host and put the host in maintenance mode if possible. - If you are unsure that NSX for vSphere is installed on an ESXi host, run this command to verify:
esxcli software vib list --rebooting-image | grep esx-*
- Look for the following VIBs to determine if NSX is installed on the ESXi host:
vsip-esx esx-vxlan
- If using shared graphics in a View environment (VGPU, vDGA, vSGA), do not use
services.sh. This shuts down thexorgservice which is responsible for graphics at the guest operating system level. By ripping the graphics out of the guest operating system, you cause the crash of your VDI workload using the shared graphics. Verify that you are using shared graphics to only restarthostd, andvpxaif you are not in maintenance mode.
See VMware KB article for additional information: Restarting the Management agents in ESXi (1003490) .
Additional Information
Refer to this video:
You can also view this video on YouTube .
Affected Products
VxRail, VxRail Appliance FamilyProducts
VxRail SoftwareArticle Properties
Article Number: 000057281
Article Type: Solution
Last Modified: 05 Feb 2025
Version: 12
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.