Monday, June 06, 2005
« Some Service-Oriented Design thought | Main | Tech Ed Speaker Auction »

Virtual PC (and/or Visual Server) are the most wonderful things to happen in a long time - especially if you use any beta software or do any system configurations that might damage or corrupt a real system.

But getting these things to run fast, especially on a laptop, can be a serious challenge. Here's a checklist of things I've been doing recently to get decent performance.

  1. Make sure to uninstall/reinstall VPC and SP1 after upgrading the host Windows XP to SP2
  2. Make sure to install/reinstall the VPC add-in software on the guest OS after upgraded to VPC SP1
  3. Put your vhd and vmc files on different physical hard drives (not just partition)
  4. If possible, put your vhd files on a different physical hard drive (not just partition) from your host OS system drive
  5. Before starting VPC, do the following on the host
    1. Stop SQL Server
    2. Stop IIS
    3. Stop any virus scanning software
    4. Stop Messenger or other IM software
    5. Close all apps
    6. Close or stop any other items in the system tray or via the Services manager - anything you can stop that doesn't crash the host is to your benefit
  6. Grant your VPC the most memory you can afford. After doing step 3, I'm able to grant 640 meg to the VPC on a 1 gig host machine.
  7. The more memory on the host machine the better. 2+ gigs of RAM rocks!
  8. If you need to put the host in standby, close VPC entirely first. Not just VPC instances, but close the VPC console itself. There are bugs with VPC that cause display failure issues when the host comes out of standby
  9. If your VPC mouse pointer ends up with a black box around it (in LiveMeeting or other projection software), go to your video settings under the Settings tab, Advanced button and turn hardware acceleration down one notch

I'm sure there are other tips and tweaks, but doing these helps a whole lot with VPC happiness!

 

Monday, June 06, 2005 2:26:36 PM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [5]  |  Tracked by:
"Rockford Lhotka on why you should buy VMWare Workstation 5" (Amped::Technology) [Trackback]
"re: Visual Studio 2005 Beta 2: Ancora Errori" (tomi) [Trackback]

Monday, June 06, 2005 2:58:48 PM (Central Standard Time, UTC-06:00)
Man I had a list like that when I was running Windows 95 on a 386 with 4MB of RAM - welcome back to the future?
Thursday, June 09, 2005 6:10:35 PM (Central Standard Time, UTC-06:00)
That's a lot of effort to get decent performance?

I use VMware 5.0 at work and VPC at home and VMWare is definitely more memory friendly and IO performance is better. Only problem is when your VM's end up taking up more than 80% of host memory you could be in trouble.

Maybe give that a go and see how the perfomance stacks up.
Thursday, June 09, 2005 9:53:44 PM (Central Standard Time, UTC-06:00)
One other tip - if you're going to run this on a laptop, chances are that putting your vhds on an external usb2.0 harddrive will give you much better performance than keeping them on the slow built-in hard drive that your laptop came with. I'm talking a world of difference here. Another bonus with this is that you can take your vhd's to other machines easily!
Friday, June 10, 2005 9:17:41 AM (Central Standard Time, UTC-06:00)
That's true, and I do that. A friend of mine has a firewire 800 external drive, and that is REALLY fast!

But make sure to keep the vmc file on the local hard drive so it is separate from the vhd.

Also, I use the WinXP feature where My Documents is mapped to a network drive and is synced for offline usage. Which is awesome, as it provides automatic backups every time I connect to my network. However, it is BAD to have the vmc in My Documents (the default) in this scenario because if you save state in the VM this massive file gets synced on your network.
Friday, June 24, 2005 5:51:08 AM (Central Standard Time, UTC-06:00)
Often I find I get a 'smoother' UI experience if I run the VPC without logging in and then use remote desktop on another machine to connect to the VPC. The results are probably pretty subjective, but some days I can't tell if I'm working locally, remotely on the network or onto a VM running halfway around the world...

- David
Comments are closed.