Like Jeff Lynch, I've been running the Virtual PC 2007 lately since my Vista RTM install. In general terms, it works just as well (or just as fair, more likely) as Virtual PC 2004. Like Jeff, I've always had the problem with the Centrino chipsets issues in Virtual PC (though in my case it's with the 950 set).
That said, I did try today adding the
Meanwhile, I did ran yesterday into an ugly issue: Doing any WPF development on Virtual PC 2007, on my machine at least, is a big no-no. Sure, I knew from the start that WPF won't really perform well under a virtual machine, and that's fine; that's not the issue at all.
The problem I noticed was that running anything on the virtual machine that initializes WPF, even if it doesn't do any animation or 3D causes Virtual PC to take a long time to redraw the virtual machine screen. Seeing the response to, say, a click on a button, takes almost one second to render on screen. It's not that you can see the screen redrawing slowly either; the screen changes instantly, it just does so one second too late.
At first I thought something might be hogging my CPU, but I checked and both the host and guest CPUs are almost idled when this happens. In fact, I went so far as to connect through RDP to the guest OS and it is very responsive through remote desktop (well, as responsive as can be expected through RDP), so it's not like the whole machine is getting slowed down; it's just the VPC display rendering.
What's so bad about this? Is not that you can't run a full fleged WPF application; it's that you can't even develop one. Opening up a XAML file in Visual Studio with the .NET FX 3.0 Orcas extensions causes the issue as well, since the XAML editor initializes WPF for rendering. So, it's editing in Notepad2 for me, I guess. I bugged this, but somehow, I'm not expecting it to make much of a difference...