After repaving my desktop machine (which is my main work machine) with Windows 7, I tried the Windows Virtual PC for Windows 7 RC to run the few Virtual PC-based Virtual Machines I still use occasionally. It worked, though I didn’t bother installing the updated integration components (formerly known as Virtual Machine Guest Additions) for a while which caused a number of issues.
This week I took a bit of time to uninstall the RC and install the RTM version of Windows Virtual PC. Notice that I have no interest in XP mode, merely in running my existing VMs, many of which are running Windows Server 2003.
A couple of things worth pointing out from this sad experience:
- Updating Virtual PC from the RC to RTM took me 4 reboots. Seriously screwed up in this day and age, but I fully blame it on…
- The ungodly bad UI that Windows Virtual PC uses. The old Virtual PC console was a bad UI, but getting rid of it and replacing it with a shell extension, and one that forces you to keep your virtual machine definition files in a specific folder and has terrible usability was an incredibly stupid choice. No wonder so many reboots are needed for any updates, since Windows Explorer will get in the way.
- After updating the integration components on my Windows Server 2003 virtual machines, imagine my surprise at seeing: (a) virtual pc locking the VM and wanting me to log in pretty often, (b) no way to change VM resolution from inside the VM and without ClearType being used to render fonts at all.
And then I remembered what causes this: Windows Virtual PC sort of ditches the old display rendering and instead will use RDP to access your VM (so you’re pretty much working in a sort of embedded RDP client). Windows Server 2003 didn’t support ClearType over RDP originally, so I went hunting for KB946633 and install it on my VM. One more restart, and ClearType was enabled.
This is supposed to be progress, ladies and gentlemen.