Welcome to Atlanta .NET Regular Guys Sign in | Join | Help

Virtual PC limitations...

I am currently working on-site and have a need to set up a virtual pc environment mirroring the clients’ production environment. Virtual PC seems to be the perfect solution. Everything has been up and running fine, but occasionally, well, always, my environment crashes and all 4 vpc’s come crashing down.

This has been a severe hindrance in moving forward as I never know when it is going to happen, just that it will.

Well I finally decided to do a little research and it turns out there is a known bug when you run multiple guest operating systems whose combined RAM configuration is larger than 2 GB. There is a deadlocking issue in the Virtual PC memory aperture list that is used to keep track of the guest operating system’s memory (this is from the KB article).

It turns out that there is a Hotfix for this and I contacted Microsoft to get it. Here is a link to the KB article.

http://support.microsoft.com/kb/887181/en-us

I hope this helps at least one person, as it has caused me a great deal of grief.

In the end the fix did not solve my problem. I had to reduce the RAM allocation of all my virtual pcs so that the total was < 2 GB and all is well.

Published Tuesday, January 31, 2006 9:26 PM by Dan Attis

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: Virtual PC limitations...

Holy Moly, a post from Dan! Way to go!
Tuesday, January 31, 2006 9:12 PM by Matt Ranlett

# re: Virtual PC limitations...

I only use VPC to do development - for mirroring production environments we use VMWARE GSX Server. I would love to have a portable with more then 2 GB however ;-) ...
Wednesday, February 01, 2006 11:15 AM by Joris

What do you think?

(required) 
required 
(required)