Virtual PC 2007 NIC driver problem

I have a VM (Windows Vista Ultimate Edition) running in Virtual PC 2007 sitting on a Windows Server 2008 host.  The guest OS system is painfully and ridiculously slow.  

My main concern is that when I boot up the guest OS it can't seem to find the network drivers.  Every now and again it will, they load up and everything is fine, but then it just "forgets" about them again and I get the (Code 10) error with no connectivity.  

Also, my CPU shows as 2.88ghz but only seems to be operating at 20mhz according to the guest Vista.  The host system I have the VM running on is 3.0G Intel with 3gb of physical ram.  I have allocated 1gb of ram to the virtual machine which should be enough for a dumbed down vista to run.  I'm not looking for AERO or anything, but currently regardless if I'm running the VM in VPC2007SP1 or VS2005SP1 it seems to eat up ALL of the resources of the host and guest machine.  

I have installed the most recent of the VMAdditions (appropriately depending on if I'm running in VPC2007SP1 or VS2005SP1) and all KB's I could find on the host and the guest to no avail.  I have reinstalled the OS 3 times to make sure it wasn't just something to do with the install and I still have the same issues.  I have some XP vm's that work fine on VPCSP1 and VSSP1 so I don't think it's the install or the host computer exactly.  Also, I have uninstalled both VPC and VSSP1 a couple times to eliminate that possibility as well.  

Any suggestions are welcome.  
jclemoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Hello jclemo,

Why are you running Virtual PC on Server 2008?  Why not run Hyper-V instead.  Virtual PC is only going to run at about 30-40% of the CPU in Virtual PC - you can get MUCH, MUCH better performance with HyperV

Regards,

leew
0
jclemoAuthor Commented:
It's a 32 bit OS and processor.. HYPER-V is only available for 64 bit OS and processor.  Also, I have tried running the VHD in Virtual Server 2005 as well with the same results.  

http://technet.microsoft.com/en-us/library/cc732470.aspx#BKMK_reqs
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
I'm not sure you are going to get much better performance than that... If you're are running on a 32 bit processor, than I'm almost certain there is no hardware assisted virtualization available so you really are stuck at an under-performing system.

I'm not sure about your networking issue - I've got Vista Ultimate on a VM on my SLOWER notebook (1.9 GHz) and it's slow... but the networking works fine...
0
jclemoAuthor Commented:
I fixed it.. I just put Microsoft Virtual Server in the garbage can and now everything works.. I can run 3 VMs running WinVista Ultimate with great performance with VMWare.. booooo Microsoft booooo
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Virtual Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.