Hello community
I'm looking for a cheap hardware solution to play with VMware ESX 3.5, or 3i. Since the new version doesn't work in the Workstation Version it's important to have an alternative
Thanks in advanced for the feedback!
Miguel
|
Here's a list I'm working on. If you're looking at a whitebox then ideally something with a broadcom / intel Pro /1000 NIC. For a SATA controller the list here should still be fine - http://www.vmprofessional.com/index.php?content=sata_faq, but ESX has a greater number of drivers on the install CD. If you open the CD, go to /vmware/RPMS/ and look for the VMware-esx-drivers-* rpms. If for example, you have a Promise controller open vmware-esx-dirvers-scsi-sata-promise-1.03-64607.i386.rpm. Drill down into the rpm until you find this file - VMware\RPMS\VMware-esx-drivers-scsi-sata_promise-1.03-64607.i386.rpm\VMware-esx-drivers-scsi-sata_promise-1.03-64607.i386.cpio.gz\VMware-esx-drivers-scsi-sata_promise-1.03-64607.i386.cpio\etc\vmware\pciid\sata_promise.xml. You can open it and then you'll see a list of SATA controllers that ESX will recognize. These aren't supported, but they will likely work. With some SATA controllers (see the source link for the HP ML115 below, you have to make some changes after the install of ESX as the controller is not listed in the XML file, but you can edit it to add support for the card. That assumes that the driver will work with the SATA controller. Processor wise if you're going with Intel make sure the processor supports Intel VT. Some of the older and lowest priced dual-core CPUs don't. If you're going with a good dual / quad core CPU then a single processor motherboard will be sufficient. You can also look for older servers that were supported with ESX 3.0.x on eBay. I have an older IBM x335/336 that work fine with 3.0.2 - just haven't tested them with 3.5 yet. Downside with them is that they don't have Intel VT so I'm limited to 32 bit VMs on them.
|
|
Hi,
best is to use any newer dual/quad core cpu (amd ot intel) and memory. Be careful which SATA controllers are on the mainboards. (as Dave.Mishchenko already posted) I bought additional PCIe (http://www.intel.com/network/connectivity/products/pro1000pt_desktop_adapter.htm) and PCI (http://www.intel.com/network/connectivity/products/pro1000gt_desktop_adapter.htm) gigabit nics. ps: Award points if you find answers helpful. Thanks. |
|
go to http://vmetc.com/2008/03/14/esx-home-lab-hardware-shopping-list/ for the parts to build a dual core AMD host for $337or a quad core Intel host for $695.
|
|
We will be starting our first rollout of VMWare in a week or two. We're using 4 top-end DELL 2950's for the physical hosts and an EMC NS20 for the storage. I would LOVE to start building a TEST environment right now and I have 3 systems exactly like the cheap AMD system posted earlier as well as plenty of storage options. However, what I DON'T have are test versions of ESX. How are y'all doing this? Are you just using your production license on test systems? |
|
My network admin told me that you could only use one "evaluation ESX" evaluation and there's not such for VC. Is he just misinformed and the "evaluation period" is like with Windows products (i.e. install it to test and just wipe it when done, no activation necessary). If that's so, I guess you have to have the "real" product first because you don't seem to be able to get more than one trial license via the website. Not being dense on purpose, just not getting how you can test the whole enchilada. |
|
The evaluation process has changed recently. It used to be that you would get a 30 day eval license for VirtualCenter 2.0x / ESX 3.0.x and the license files would expire and be unusable after that period. Now with VC 2.5 / ESX 3.5 each product will start with a 60 day eval so in theory you could just reinstall on your test systems every 60 days. Not sure what the evaluation license agreement says about that though. When you install and leave it in eval mode you don't have to worry about adding a license file as you would have with VC 2.0.x / ESX 3.0.x.
|