Does anybody else install win2008 as a virtual machine, and witness it devouring processor cycles doing the simplest of chores, like using WE?
I thought it was some “freak incident” when i was trying out the first beta, which effectively made it unusable. It took some 13-14hrs to install SQL Server 2008 only to report failure to install at the end. Now that I am installing the RC build, i thought those troubles would go away, but apparently it is behaving quite similar to the beta. Is this some indication that win2008 does not run well on top of Virtual Server 2005 (R2)?
UPDATE
I copied the VMC out of my server onto my [more powerful] desktop computer, ran it under VPC2007 with VMA 13.803 and seems to "behave" itself now. Although the weird thing is i installed the x64 version of VPC2007 and Task manager registers it as Virtual PC.exe*32. Unless it is just a 32-bit binary optimised for x64 use.... anyway it still does claim quite a high amount of CPU for other chores like running SQL Mgmt Studio.
A friend has pointed out I probably should use Virtual Server 2005 R2 SP1 with VMA 13.813. I tried that but the situation does not change.
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral