But wait there’s more. In a perfect world every virtualization lab would be done on server grade hardware. Reality is different for personal purposes some of us use desktop hardware which is cheaper but also limited in some ways. Consider this post to be simple advice from a simple man, ahoy!.
Dual core is the standard by now, so why not try to go for a tree or four core CPU if you can. Anyway two cores will work in most situations.
Along with others I believe Intel has segmented part of the CPU market by not making some of the cheaper CPUs VT capable. AMD offers a capable and affordable line of two, three, and four core CPUs, time to go cherry picking. Note: I don’t dislike Intel, it’s just that I wanted to save some money.
32bit guest will run on limited memory. Try to do the same with multiple 64bit guests and you will have a different story. RAM is cheap.
In a perfect world the system would make use of a RAID controller capable of RAID10, due to high cost that’s not the case. That’s why it’s recommended you separate the host OS from the virtual machines, the load may become unbearable on a single disk that has to do the job of two.
This may depend on whether you are planning to run a desktop OS or server OS, remember if you go with 32bit OS you will find your self limited to 4 GB of physical memory. With that in mind if want to run multiple 64bit virtual machines you will find your self limited. Anyway 64bit is the future, get use to it.
The correct motherboard means: 4 memory slots and above. Buying 4 x 2GB memory modules is cheaper than buying 2 x 4GB memory modules. Multiple SATA ports means more hard drives to store virtual machines or store backups.
It’s a good idea to know or guess the expected load each virtual machine will bring to the system. All too often people assign as much as they can to a virtual machine without realising it might impact the host. Don’t assign multiple CPUs just because you can and go crazy with storage you might need it later. Feel free to provide more recommendations.
lab, virtualisation — Nov 11, 2009