Hi All,

Recently I joined a new company who still had packaging and test PC's as physically separate devices, i.e. no virtualization. I proposed to change this to a high-spec workstation and use virtual machines for packaging, testing, etc.

I've finally been given the go-ahead to order a high-spec workstation (HP) and was wondering if anyone has went through the same process and had any advice or gotchas to be aware of?

My initial thoughts are:
64-bit Dual Core processor
4GB RAM
2 x HDD's (one OS and second for pagefile, VM's etc.)

Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If you're going 64-bit (and presumably you'll opt for a 64-bit OS for the host) why stop at 4Gb? I'd bump that up to at least 8Gb.
Answered 03/29/2010 by: VBScab
Red Belt

Please log in to comment
0
You're quite right, the more memory the better with VMs [:)]
Answered 03/29/2010 by: fritoz
Orange Belt

Please log in to comment
0
This might not fly but running VMs on a solid state drive is a very positive experience. I do it for my laptop but if I client is willing to spend some $$$ on their internal environment I suggest it. My opinion is that you can either pay me to do work or be cheap with the hardware and pay me to watch progress bars.
Answered 03/29/2010 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Funny you should mention SSD's, I was configuring a workstation on HP's site and I saw one as an option, like you say pricey though over time a wise investment with the money saved.

How is your system configured? Is the SSD a separate drive specifically set aside for VM's or do you just have the single SSD only with OS, apps and VM's all running from it only?
Answered 03/30/2010 by: fritoz
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity