How can I adjust the "robustness" of my VMs?

I've running Windows 7 x64 Quad-core laptop (4GB) along with 2 VMs running W2K3 (1GB, 800MB respectively). The amount of time I spend in the VM waiting for the cursor to catch up to my typing is really getting annoying. Half the time I don't see "as I type" and then after a sec. pause, it all shows up. Very high latency. Ok, I am running VS2008 in a VM, but still.

What can I do to improve "robustness"? Any help, pointers, URLs appreciated.

UPDATE: Running Windows 7 Virtual PC. Yes, I've installed integration features. I'm wondering if you can get millisecond performance out of VMs (things like having Visual Studio keep the cursor synced with your typing), or if I'm just asking too much.

Hi there

Go for VMWARE SERVER -- it's FREE and DO install the add on vmware tools (in the GUEST machines).

If you can afford it - go for vmware workstation rel 7 to get the latest version of vmware tools. A trick is to get the trial so you can update to the latest version of vmware tools then go back to vmware server. Vmware workstation will prompt automatically for you to install the new vmware tools the first time you start the guests. This version has fixed a lot of Video and mouse performance problems and even has a basic level of 3-d rendering.

I'm running TWO concurrent guest W2K3 server machines on a 4GB system (really need more RAM but this machine only has 2 slots in the mobo).

These machines are running SAP systems - ERP type of stuff so heavyish load - and they are really fast and stable.

Here's a screen image -- was also running Windows Media center with a TV card on the host.

The advantage of using vmware server is that the VM's can run as background processes so you can log on to applications on your Virtual Machine guest without initiating foreground sessions / processes -- this makes for much better use of HOST resources.

The other advantage in using vmware server of course is - especially when running a GUEST server as a virtual machine is that different users can log on to the guests when required - you don't need to start these virtual machines via a user session on the HOST. They can also be started automatically whenever the host is re-booted as well as system tasks.

This also means you can effectively use your W7 HOST system as a decent server.

For running W2K3 servers as a VM's I'd junk Virtual box in favour of vmware server.

(To the OP - if you do it this way you can eliminate the VS2008 virtual server eliminating another layer in your process. By running vmware server you are effectively doing what the vs2008 server is trying to do in your setup. After starting vmware server on the HOST you (or any authorized user) will be able to access your W2K3 servers and any applications on them from ANY machine in your network without needing a logon or user id on to your HOST Windows X-64 system

If you want to test VS2008 that's another matter but why not also test this in its own right without loading up other servers on it. Just fire it up via vmware server and test your applications directly on it.

IMO W2K3 server - especially R2 is still fine for loads of apps - I won't be getting rid of it any time soon.).



Cheers

jimbo