[ QUOTE ]
The deployment server is a p2v copy of our original server running on VMware ESX server.
[/ QUOTE ]
Yuck! My sympathy! Our lan group has also succumb to VM-Ware fever. Every time we ask for a new server they try to shove VM-Ware down our throats. We have tried out VMWare deployment servers. They stink. Go back to a real server.
I have a vm-ware batch server. It's substantially slower than a physical box. I live with it because it supports our PY and DV environments only.
I have a VMWare fat client. It is substantially slower than a physical computer. Since I don't use it very often, that is acceptible.
I have one VMWare terminal server. If tuned correctly, it can hold it's own against a physical terminal server. Attached is an analysis of a vm-ware terminal servers vs. physical servers. As you will see, if not tuned correctly, it performed poorly.
I am trying out VMWare for hosting IBM Websphere 5.02 and JAS. That expiriment bombed right out of the gate. After fifteen tries, I could not even begin to load Webshere on that box. I kept running into memory errors loading the Java Client. I gave up and went physical.
Don't even think about VMWare for a production Enterprise server.
VMWare has it's place for test boxes and other low-end, no high performance needed, applications. Just keep it the heck away from my production JDE servers. It cannot handle the load.
Gregg Larkin
JDE System Administrator (CNC) / North America
Praxair, Inc.