Yousuf said:
It's listed as ACPI PC in the virtual machine. Would I be able to simply
change it to ACPI Multiprocessor?
According to the Wikipedia articles, Virtual PC only emulates a Pentium
II processor, so I don't know multiprocessing support is available on
such an old processor family.
BTW, it's listed as a product by Connectix, but does Microsoft own it now?
I'll have to keep that in mind.
Yousuf Khan
Microsoft bought Connectix some time ago.
*******
All I can suggest for that bogus Wikipedia information, is
to check in Device Manager of the WinXP guest OS and
look at the Computer entry. You say that is "ACPI PC",
and that is similar to my single core laptop which is
listed as "ACPI x64 PC".
When viewing the computer entry, if you attempt a driver update,
and list the existing drivers, there will be a list of HALs
that can be installed in place of the current HAL. On my laptop,
when I do that (because it has a single core), I see only the
"ACPI x64 PC" offered as a driver update. No other option.
If I had a multi-core processor, there would presumably be
more options.
I can see by looking at this article, that Windows Virtual PC is
indeed still a single core environment. There are basically
no driver options in this case. "ACPI PC" = doomed.
http://support.microsoft.com/kb/309283
"Advanced Configuration and Power Interface (ACPI) PC," ACPI PIC HAL (Halacpi.dll)
* Standard PC <--- Do not use.
* Advanced Configuration and Power Interface (ACPI) PC <--- Your existing HAL
If you were to request a driver update, and check the list of
available drivers, those are the two you'd see. And you
definitely do *not* want Standard PC, as that disabled ACPI
and really makes a mess. So basically there is only
one realistic option in that case, which is the HAL currently
being used.
If you saw this in Device Manager:
"ACPI Uniprocessor PC," ACPI APIC UP HAL (Halaacpi.dll)
then that has more options when you go to update the driver.
Sitting back here, Windows Virtual PC looks to be just as
bad as VPC2007. So that Wikipedia entry for SMP must be wrong.
Checking another article, they claim Windows Virtual PC is
threaded, such that each guess OS gets its own thread, but
I don't think anyone gives a rat's ass about that. I found the
lack of improvements and the ribbon style interface change to
be such, I gave up on it. (I can't run WinXP Mode, and
I tested just the Windows Virtual PC part of the package,
and I'd sooner be running VPC2007 personally. It has the same
flaws when I install Linux as a guest, as VPC2007.)
The processor name string may say "Pentium", but the emulation
is not restrictive enough to prevent non-Pentium instructions
from running. Some multimedia software will be able to detect
several flavors of SSE. I don't know the details of what they
do with privileged instructions, whether those return fixed
emulated results, or offer to "passthru" the real processor
info (but in a protected way, so the VM can't "leak out").
Paul