Originally Posted by Oranuro
For VM's outside of your own box?
Software(I prefer VirtualBox)>Memory( Allocating 1GB+ea. makes them snappy and the hard disk won't bottleneck so much from swap)>Hard disk for ea. VM(2 per works too)>Good RDP client( I prefer to dualboot into a linux environment for it seems less laggy and seamless) for maintenance/updates, standard manipulation. A kvm would work too.
Dedicated network cards also open up of a lot of possibilities if you would like to use these VM's outside of you internal network. The eMachine would work but building your own box would provide better results and expansion. For a long time I just used my only pc to play with VM's and have learned a lot just firing up a couple with decent hardware.
I love virtualbox: it's great for quick experiments while you're in Windows and also doing other stuff. But this box has another purpose:
My work uses a CentOS 5/Xen combo. I've been there for six months and still feel like I barely know anything about Xen. So this is going to be my experimental Xen box. As guests I think it will have various flavors of Linux, some Windows and whatever else comes up. Perhaps one machine can be used as an iSCSI target, I don't know. Anyway I have my Xen box, let the time wasting begin
As for PSU I have an existing one from a former PC build I am not using any more, I don't remember the details of this particular PSU. Probably 500 watt or something. More than suffecient I should think. I also bought this new box because Xen requires the "VM extension" on modern CPUs. My old AMD 3800+ does not have that.
Can't think of a reason I would need more than one physical NIC. Wasn't planning on hooking it up to the internet seperately or anything. I do actually have an PCI 10/100 NIC I rescued from an old dell but I have other machines that could use that
I'll probably just setup an SSH daemon and webmin for the interaction with it. Won't be any GUI on this box directly so it won't be a big issue I don't think.Edited by subassy - 3/9/11 at 9:08pm