Solved

Numbber of ESX 3.5 Cloned Hosts

Posted on 2011-02-17
7
371 Views
Last Modified: 2012-06-21
Does anyone have a suggestion or guideline for a limit to the number of VM Clones that can run on 3.5 ESX Host?
0
Comment
Question by:AminNaserpour
  • 3
  • 3
7 Comments
 
LVL 28

Expert Comment

by:bgoering
ID: 34920602
Guess I am not sure what you mean by clones in this instance,, but the number of virtual machines will depend on a number of factors. Amount of CPU, Memory, I/O resources, etc. that are available on the host divided by the average workload of the virtual machines that are to run on the host.

You would need to identify which of the resources will be the bottleneck in your shop and use that to limit the total number.

Everyones results will vary.

Hope this helps
0
 
LVL 119
ID: 34920603
We've seen a farm of ESX 3.5 with 350+ with VMware View and VDI. Provided you've got the storage, CPU, and memory resources.

At an average of 64 - 100 VMs per host server.
0
 

Author Comment

by:AminNaserpour
ID: 34923041
Hi Guys

you mean thelimitation is based on Hardware ?
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
LVL 119
ID: 34923049
Yes, the limitation is based on the resources that the hardware has, normally memory in the host server.
0
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 50 total points
ID: 34923080
The Maximum number of virtual machines per ESX 3.5 host is 170.

I've personally seen 133 VMs per host.

This is as defined by VMware in this guide

http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_config_max.pdf

I couldn't find a U5 guide!

0
 
LVL 28

Expert Comment

by:bgoering
ID: 34925846
It does depend on the number of cores available. From: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007041

"vCPU per Core Limit Now at 20: The limit on vCPUs per core has been raised from 8 (or 11 for VDI workloads) to 20. This change only raises the supported limit. The change does not include any additional performance optimizations. Raising the limit allows users more flexibility to configure systems based on specific workloads and to get the most advantage from increasingly faster processors. The achievable number of vCPUs per core will depend on the workload and specifics of the hardware. It is expected that most deployments will remain within the previous range of 8-11 vCPUs per core. For more information, see the ESX CPU Considerations section of the VI3 Performance Best Practices and Benchmarking Guidelines. "

This was the update that expanded capacity for ESX 3.5. So if you have two 4-core processors for a total of 8 cores - then you could have 160 single vCPU vms running on the box. Most folks hit a memory limit well before then though...
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34925910
Ah - and that all is further limited by the 170 vms per box that hanccocka noted abover.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
In this article, I will show you HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, using the VMware Host Client. The virtual machine has Windows Server 2016 instal…
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question