The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)
View by Article ID
Checking for insufficient memory resources in vCenter Lab Manager
Symptoms
Deploy using unfenced mode fails
You see this error:
Not Enough Managed Server Capacity (Memory) Could not find a valid Managed Server due to: Insufficient memory or machine slots. This deployment requires <###> MB memory
Deploy using fenced mode fails
You see this error:
Not Enough Managed Server Capacity (Memory/Slots) Could not find a valid Managed Server due to: Insufficient slots. This deployment requires <###> MB memory and <###> slots
Resolution
This error condition is usually caused when the deploy action attempted exceeds the resources available on the destination ESX host.
To determine the total amount of memory required for the deploy action:
From the Lab Manager interface click Workspace.
Move the cursor over the configuration name and click Details from the menu.
Move the cursor over the virtual machine name and click Properties from the menu.
Note the value in the Memory field and add each value for each virtual machine to obtain a total.
Add 32MB for each virtual machine for overhead.
If deploying in fenced mode, also add an additional 32MB.
The formula is this:
Memory configured for each virtual machine + 32MB per virtual machine + 32MB for each fenced virtual machine + the reserved memory amount configured = Total memory required for deploy
Note: Each ESX host must have enough capacity for at least one virtual machine in the configuration. Deploying a configuration in fenced mode places all the virtual machines on a single server, therefore at least one server managed by Lab Manager must have enough free capacity to host all of the virtual machines in the fenced configuration.
Determine the total amount of memory available for deployments in Lab Manager:
Click Servers.
In the Managed Servers view, view the Memory (MB).
Memory – Displays two numbers separated by a slash (/). The first number indicates the amount of memory that the server is using to run virtual machines. The second number indicates the maximum amount of memory available or allowed to be used to run virtual machines.
To determine the amount of Reserved Memory:
Click Servers.
Move the pointer over the server name and choose Properties from the menu.
Observe the item Reserved Memory (MB). This setting indicates the amount of memory set aside for virtual machines not managed by Lab Manager. Lab Manager can use any remaining memory.
As an optional step, verify the memory reported to Lab Manager by each Lab Manager agent on each server:
<cpu_modelname>Intel(R) Xeon(R) CPU E5335 @ 2.00GHz</cpu_modelname>
<swap></swap>
<disksize>5036</disksize>
<diskused>1451</diskused>
<smbcapable>yes</smbcapable>
<nfscapable>yes</nfscapable>
<fencecount>0</fencecount>
</root>
The value in the <memory> field above is the value that is reported to the Lab Manager server by the agent.
If these values are not as expected, or do not match the values displayed in the Lab Manager web interface, the VMware LM Monitor service may not be functioning correctly. Restarting the service may resolve the problem. For more informaiton, see Managed Servers page is not updating/refreshing (1002673).
