ESXi server wth 140 VMs

Posted on 2012-03-18
Medium Priority
Last Modified: 2012-03-20
Looking for some advice on building an ESXi server with about 140 VMs networked to one VM sever for a testing labs.

VMs will consist of:
1 - Server 2008 (with MS SQL Enterprise ed)
     (light server activity)
139 - mix of Win 7, Win XP
       - 584 MB each, 640 x 480 video

The greatest bottle neck will obviously be I/O (especially during boot up) there for boot ups will be scheduled in a logical sequence.

Physical hardware:
Quad core I7's with max of 16 GB

1. Since I don't believe it is practical to do this on one ESXi server, how many hosts do you think are necessary?
    I am thinking 8 VMs per core for a total of 32 VMs per host; less on the ESXi server
    hosting the Win 2008 server VM

2. I will need to network the ESXi servers together. Any special considerations?

3. What do I need to purchase from VMware to accomplish this? ESXi is free. Vsphere
    (the free version can only handle one ESXi at a time). Can I manage all the ESXi
    servers from VMware 8 (workstation s/w)? Will I need to purchase anything?

Thank you
Question by:sconnell
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 122
ID: 37734998
1. Approx 6 ESXi Servers.

2. I/O is the killer, and you may want to consider Fusion I/O cards as SSD Storage to avoid broadcast storms.

3. If using free, you will need to create access to the VMs using RDP and name RDP VMs. Otherwise you will need Licensed VMware Sphere and VMware View.

You can connect to each Server individually, using the vSphere Client, but trying to manage more than two servers, that way is difficult but possible. Otherwise you will need to purchase VMware vSphere Licenses and vCenter Server.

The biggest issue with free is its limited to 32GB per server.

2GB for Windows 7, you'll only get 16 VMs per Server!

You physical server memory is low, and make sure its on the HCL.

Author Comment

ID: 37735196
Thank you Hanccocka!

Great answers!

Microsoft's minimum memory requirements is:
"1 gigabyte (GB) RAM (32-bit)"

Really? I wonder if anyone has tried with less? BUT I guess I do want to avoid any memory swapping!

I had forgotten about Windows 7 requiring a lot more memory than Windows XP. Thanks for the reminder! Because of that, I will have to minimize the number of Windows 7 workstations.

My choice will likely be SATA or SSD and it looks like SSD is really the only way to do this in order to make this somewhat usable.

>Otherwise you will need to purchase VMware vSphere Licenses and vCenter Server.

Any tips?

I haven't purchased a VMware [server] product in about five years. A quick glance at their purchase options was a bit bewildering. But I haven't had breakfast yet... maybe that is it. :-)

Thanks again!
LVL 122

Accepted Solution

Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 37735260
Using the free version you are going to have to purchase more servers to meet your 140 VM requirement because of the 32GB limit of the VMware vSphere Hypervisor (ESXi) which is limited to 32GB per server.

We've had many issues in this area with VDI deployments, when using conventional storage, either local SAS or SAN based storage. For our VDI deployments we now use Fusion-IO products (SSD) based, to save on electricity, air conditioning, the expensive of SAN deployment, and help us with "VDI storms". e.g. big slowdowns that can occur when a lot of users log into the system at the same time.

Once users boot up, log in and load applications, the storage I/O typically settles down to a minimal level. The IOPS difference between a desktop VM that is booting and after it has booted is extreme, which can make architecting storage for VDI environments a challenge.

A typical desktop VM running Windows 7 will generate from 50-100 IOPS while is it booting; once it is running normal workloads, the average IOPS drops to about 5-10. Therefore, to successfully meet the I/O demands caused by boot storms, your storage needs to be designed to handle the worst-case scenario.

Here are some real world stats taken from College based deployment of VDI (we used VMware View as the broker and Wyse P20 Thin clients), but these stats will be the same for standard ESXi server.

Dell R810 128GB 24 Cores handle 80 - 100 concurrent VMs per host server.
Software deployed Windows 7, Microsott Office to College Students.

Dell R610 48GB 8 Cores - 20 desktops comfortably.
Software deployed Windows XP 1 vCPU, 1G RAM, Microsoft Office to College Students

We are just upgrading and testing the above environment, to Windows 7, 2 vCPU, 2GB RAM, and the load has dropped to 10 desktops per server.

We've have VDI requiring far greater resources, CPU, Memory and Storage compared to Terminal Services.

We used to be able to get 75 concurrent student sessions, on a HP DL360G5 Dual Processor Quad Core, 4GB RAM with WIn2k3 and Citrix Presentation Server 4.0/4.5.

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.


Author Comment

ID: 37741650
Thank you for your excellent advice!

I do find it odd, however, that I have not found [on Internet] any other scenarios similar to what I am trying to accomplish.

>Using the free version you are going to have to purchase more servers to meet your
>140 VM requirement because of the 32GB limit of the VMware vSphere Hypervisor
>(ESXi) which is limited to 32GB per server.

I finally spoke with a VMware rep earlier today. It appears that VMware does not have a pricing model that fits what I am trying to accomplish. Everything they have is overkill and way too expensive.

So... my only alternative is to use the free ESXi and the free VSphere.
Build about 7 ESXi servers (each with 16 GB RAM, 128 GB SSD drive) with about 20 workstations on each.

Then I will manage the ESXi servers, one at a time, with the free VSphere. This should not present a problem because I will not need to *ever* log into the workstations after their initial set-up.

Does not make sense?

Thanks again!
LVL 122
ID: 37741813
It  makes sense, if you want to proceed because of budget constraints.

Author Comment

ID: 37743108
What is the best way to clone and deploy 140 workstations across 7 ESXi servers.

Author Closing Comment

ID: 37743114
Thank you very much for your valued help.

Featured Post

Don't Cry: How Liquid Web is Ensuring Security

WannaCry is just the start. Read how Liquid Web is protecting itself and its customers against new threats.

Question has a verified solution.

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

A look into Log Analysis and Effective Critical Alerting.
WARNING:   If you follow the instructions here, you will wipe out your VTP and VLAN configurations.  Make sure you have backed up your switch!!! I recently had some issues with a few low-end Cisco routers (RV325) and I opened a case with Cisco TA…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
Suggested Courses

801 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