On vista with some fancy multi core machinesâ€¦ Iâ€™ve found that some OSâ€™s will just DOG big time, inducing major latency, disk errors, and of course itâ€™ll eventually corrupt the guest OS into not working.
As an instance, NT 3.1 takes about 30 minutes to install (compare to Qemu in about 2 minutes tops) and every time Iâ€™d try to convert the disk to NTFS it would either corrupt the disk so it couldnâ€™t boot or it would fail saying the disk was unable to convertâ€¦
Anyways back when Virtual PC was a connectix product it was meant to run on a SINGLE CPU/CORE. Back then multiproc machines were serversâ€¦ And who would be running Windows NT 4.0 server on a Windows NT 4.0 server??
Anyways the â€˜fixâ€™ here is to set Virtual PCâ€™s affinity to a single core BEFORE you start any VMâ€™s. Iâ€™ve been setting mine to 0, but i suspect it doesnâ€™t matter as long as no other VMâ€™s have started before hand. Anyways start up Virtual PC, then launch task manager, and set itâ€™s affinity to a single core, then youâ€™ll be good to go!
So far it would seem that Virtual Server is not hit by this, and I have to wonder if you install Virtual server onto a machine running Virtual PC with the new â€˜coreâ€™ would it work correctlyâ€¦..?
Anyways this fix is good enough for me. Itâ€™s nice to boot up in a few seconds.