MowGreen said:
Windows Virtual PC is intended for system's whose CPU supports
virtualization. It's meant to replace VPC 2007.
From the download page -
http://www.microsoft.com/en-us/download/details.aspx?id=3702
" Supported Operating System
Windows 7
Processor: Intel®, AMD®, VIA® processors capable of
hardware-assisted virtualization, with the setting turned on in the
BIOS. "
As for performance, I've never used it as my CPU does not support
virtualization.
It only supports "reality based applications".
MowGreen
================
*-343-* FDNY
Never Forgotten
================
One difference, between VPC2007 and Windows Virtual PC, is the
former has a "nice GUI" for controlling the setup, whereas the
latter has a dreadful "Windows 7 look and feel" interface for the
same function. You can hardly figure out where your VM went. As
a test, I think I tried running some Linux VM in there.
It's bad enough, I uninstalled Windows Virtual PC from my Windows 7
laptop.
Windows Virtual PC, also supports running WinXP Mode. To do that,
it had support for Terminal Services and Remote Desktop Protocol
added. That allows seamless operation of a WinXP staged program,
as a window floating around in the Windows 7 desktop. If you
were doing that from VPC2007, you would have a window drawn around
the entire WinXP desktop, and all programs would appear inside
that desktop view. Whereas, with Windows Virtual PC + WinXP Mode (500MB
download), you get WinXP programs mixing with Windows 7 programs,
on the desktop. And the windows are drawn as if they were from a
"remote session".
http://en.wikipedia.org/wiki/Windows_Virtual_PC
On VPC2007, hardware virtualization support via VT-D/AMD-V was optional.
You could enable or disable that on a per-VM basis. This caused no
end of problems with Linux VMs, because they would test for this,
from inside the VM. And because the code was buggy as hell, they'd
crash. The latest Linux abortion, was incorrecting identifying
VPC2007 as Hyper-V, looking for Hyper-V disk drivers, finding none,
and then refusing to access any virtual hard drives in the Linux VM.
That took a whole year for them to fix, and is just starting to
trickle out as a bug fix.
On Windows Virtual PC, according to the above Wikipedia article, the
initial release of the software required VT-X/AMD-V. But apparently
that was relaxed somehow.
"System requirements for Windows Virtual PC
Optional: if the processor supports hardware-assisted
virtualization technology such as AMD-V or Intel-VT, it will
be used. Before March 19, 2010, such a processor was mandatory."
And the latest snafu, is on Windows 8, they include a copy of
Hyper-V for free (replacement for virtual pc series of software).
But it requires SLAT, otherwise known as Extended Page Tables.
And I don't have any processors here with that. When I tried
to install Hyper-V, it failed silently, and it was only later
I noticed the error message.
So every version of that software that was free, has had some
complicating hardware issue introduced, for no good reason.
The Hyper-V issue is the worst of it, so far (no workaround).
Paul
