Running Virtual PC 2007 on VMWare Player

I’ve always liked Virtual PC, and it was a shame IMHO when Microsoft twisted this fantastic utility in some glorified IE6 box, A’la “Windows XP Mode” for Windows 7.

So I downloaded and installed VMWare Player, as I’ve heard you can use it to run ESX among other things requiring hardware acceleration, and  player fits the bill for being cheap.

Passing the hardware acceleration to a child VM is a matter of checking a single box in the settings.  Namely the ‘Virtualize Intel VT-x/EPT or AMD-V/RVI” box.  Although you don’t have to click it if you want, it just offers greater performance.

Windows XP x64 setup

VMWare Player

Now I installed my old copy of XP x64, as I felt like something different, then I went ahead and installed Microsoft Virtual PC 2007 sp1.  The installation was pretty uneventful.

Now with that out of the way, I could setup a VM,and I decided to install OS/2 1.21 for the heck of it.

OS2 1.21 on virtual pc on VMWare player

Virtual PC running OS/2 1.21 without hardware acceleration

And it booted up no problems, like it did back in the XP days.  I even ran it with and without CPU acceleration and it works on both, but is noticeably faster with acceleration.

With Intel-VT acceleration

With Intel-VT acceleration

So I thought this was interesting, although Virtual PC has been essentially dead ended, it can go on with an older OS in a VM, to let you run VMs.

I would imagine that if VMWare Player could run Virtual PC 2007, that 2004 should work as well.

This entry was posted in OS/2, Virtual PC, virtualization, VMWare by neozeed. Bookmark the permalink.
avatar

About neozeed

What is there to tell? I've loved UNIX like things since I was first exposed to QNX in highschool (we had the Unisys ICONS!), and spent the better time of my teenage years trying to get my own UNIX... I should have bought Coherent in retrospect.. Anyways latched onto Linux in 1992, and then got some old BSD admin books and have been hooked on the VAX BSD & other big/ancient things since...!

26 thoughts on “Running Virtual PC 2007 on VMWare Player

  1. Nice. I currently also run VPC 2007 and the older VirtualPC 4 (before it was a Microsoft product) in VirtualBox, where it runs nicely as well. I’ve been experimenting with a number of virtual machines within virtual machines and find it is a nice way to preserve older, unsupported software, but I never did test VMWare player.

    @ampharos – I’ve set up a “virtual xp” 32-bit guest inside of VirtualBox and I’m able to run Windows Mobile 2003 and 2003 SE in that system. I’ve also had success running Windows Moible 5 – Windows Mobile 6.5 in a virtual Vista guest under VMWare Workstation. I think those later versions may have required Vista or later?

    • I always remember getting some error saying you shouldn’t be doing this… Somewhere I think I still have a copy of Connectix Virtual PC that’ll run on NT 4 somewhere… I think.

  2. I played around with VirtualPC 2004 running on the Windows XP guest machine in VirtualBox and it’s operating pretty good, although, it’s slow with hardware virtualisation enabled.

    I’m wondering if it’s possible to get VMware Player and DOSBox running inside VirtualBox.

    I have a lot of disk space remaining on this computer…so, I might consider using hard disk images on shared folders. :B

    • DOSBox doesn’t have hard CPU hooks that I’m aware of so it should run under pretty much anything..

      Also I think VPC 2004 only requires a Pentium III, So I think it may even run on machines without VT… But I’m not 100% on that.

      • The latest version of VMware Player tested under VirtualBox is version 3.1.6. Starting with version 4, VMware Player will refuse to install, because it requires various CPU instructions that are not present in the VM-emulated CPU.

        DOSBox should run okay under VMware, VirtualBox…even VirtualPC. However, if you want to use mouse support, VM mouse support has to be disabled.

      • Try setting the OS for VirtualBox to Windows 8.1, as that enables a bunch of extra virtual CPU features (it’s also possible to enable them manually with vboxmanage command, but changing the virtual OS is simpler).

  3. I’ve played around with various nested virtualisation setups mainly for fun, but occasionally also to get an OS to run which refuses to play nice with the “outer” hypervisor.

    The configurations I tried were:

    – Hyper-V (2008 R2) in VMware Fusion 4 (slow using XP guest as the nested/second-level guest, much faster using 7)
    – Hyper-V R3 (Win8 Beta) in VMware Fusion 4 (nested Win7 guest faster than XP)
    – KVM in VMware Fusion 4 (nested Win7 faster than XP)
    – Parallels Desktop in VMware Fusion 4
    – Qemu in Qemu in VMware Fusion 4 (ok, that’s not nested virtualisation)
    – Virtual PC 2004 in VirtualBox in VMware Fusion 4 (didn’t work)
    – Virtual PC 2007 in VMware Fusion 4
    – Virtual Server 2005 R2 in VMware Fusion 4
    – VirtualBox in VMware Player in VMware Fusion 4 (unusably slow)
    – ESXi in VMware Fusion 4
    – VMware Player 4 in VirtualBox
    – VMware Player 4 in VMware Player 4 in VMware Fusion 4 (unusably slow)
    – VMware Workstation 8 in VMware ESXi 4
    – VMware Workstation 8 in VMware Fusion 4
    – Xen 4 (from Debian 6) in VMware Fusion 4
    – XenServer 6.0 in VMware Fusion 4 (quite slow using an XP guest)

  4. I’ve found that stuff to be quite addictive 🙂 The ability to virtualise VT-x has been there since VMware ESXi 5/Fusion 4/Player 4/Workstation 8 but was a hidden feature in Fusion and ESXi first.

    • you think that would have been a feature to shout about, but for some reason VMWare keeps that stuff under wraps, or barely mentioned…

      • Yeah, I’ve often noticed that while Fusion has the same features as Workstation, the more “interesting” ones are likely to be hidden and only accessible by editing configuration files. Nested VT-x is one example, creation of a DHCP-less host-only network is another in the case of Fusion 4. On the other hand, with Fusion being significantly cheaper than Workstation, that may be purely intentional.

      • I’m pretty sure that VMWare uses the same virtualization kernel in all of their products, it just packages it differently.

        Hint: create an empty file (0 bytes in size), set it as floppy image, and tell VMWare to boot off it.

      • I’m pretty sure it’s the same as well… But I’m too scared trying to boot off an empty file… I suspect it’ll end poorly.

  5. Forgot to add two nested setups I’ve used successfully to the list:

    – SCO Merge 4.1.1 in VirtualBox
    – Netraverse Win4Lin 5.0 in VirtualBox

  6. Looking at your screenshot, are you using Windows 7?
    I have VirtualPC 2007 running just fine under native Windows 7.
    I was wondering what kinks you ran into if it doesn’t work for you.

    • I know you have to swap some device driver out with another one from some windows ce emulation thing (that was virtual pc, before MS gutted a fine product).

      I just haven’t bothered trying to load it natively… I was more interested in VPC 2004 actually as it can run NeXTSTEP 3.3 pretty well.

  7. Running a virtual PC does not give as a full featured PC! It has so many limitations. I personally do not enjoy it.

    • I don’t think you understand how versatile virtualization is. Some of us don’t have the space for 30+ machines.

      • Fun stuff. I tried installing VMware Workstation 1.0 in a VM once but sadly didn’t get very far with it due to a plethora of errors it spat out at me.

      • That is really too bad. But strange enough that it’ll run ESX. I should dig out my old ESX 2.5 stuff and see if that works.

Leave a Reply

Your email address will not be published.

Notify me of followup comments via e-mail. You can also subscribe without commenting.