Are VHDs compatible between Hyper-V and Virtual Server and Virtual PC?

This question frequently comes up, but most often is not the question people mean to ask. As written, the answer to the question is yes – there is no change to the VHD format specification used between any of these virtualization solutions. The real question usually is:  “If I build a virtual machine on a VHD in one virtualization solution, will it be compatible with another virtualization solution”.  This blog post focuses on answering the revised question. As you’d expect, the answer isn’t that straightforward.

Let’s start by looking at the obvious cases where the answer is “No, they are not compatible”. Assume you build a virtual machine using Hyper-V, and it is 64-bit. Here, the answer is no as Virtual Server and Virtual PC do not support 64-bit virtual machines.

What about a 32-bit virtual machine built under Hyper-V? Generally the answer is again no. This is because most operating system will detect the presence of an IO-APIC in the virtual machine environment and install an appropriate HAL in the operating system image. Once that image is started on Virtual Server or Virtual PC where an IO-APIC is not present, the image will fail to boot. In theory it is possible to swap the HAL, but not in a Microsoft supported manner (except on Vista and Windows Server 2008 – that’s a post for another day). So the answer remains no. [Maybe an exception would be where an operating system is able to dynamically switch between IO-APIC and PIC modes (this is not the case in Windows Server 2003 or Windows Server 2008 or any OS I’m myself familiar with). I guess that some Linux flavours with appropriate boot switches may be OK, but I’m no expert in this area.]

Now let’s look at some “yes” scenarios. These are the ones where the virtual machine is built under Virtual PC or Virtual Server initially. If you take a VHD image and create a new VM in Hyper-V usng that VHD and simply boot it, yes, it will be fine. If you do not install the Integration Components and subsequently take the VHD back to Virtual PC or Virtual Server, yes, it will also boot fine.

Following on from the previous paragraph, if you install the Integration Components (and let’s stick to Windows Server 2003 for the example), then we swap the HAL to an APIC HAL as the first part of the installer. At this point, the VHD will no longer boot under Virtual PC and Virtual Server.

Hopefully that helps!

Comments (29)
  1. Anonymous says:

    Honestly I was shocked when I read John's recent post about " Are VHDs compatible between Hyper

  2. Anonymous says:

    John has posted a good blog entry describing how to make vhd image work between VPC/Virtual server and

  3. Anonymous says:

    Honestly I was shocked when I read John's recent post about " Are VHDs compatible between Hyper

  4. Anonymous says:

    Lately it’s been very quiet on my blog. There are a couple of things to that. First and foremost there

  5. Anonymous says:

    There is one particular scenario where you could be faced with this when booting a VM using Hyper-V.

  6. Anonymous says:

    Ja det går alldeles utmärkt att boota en VHD fil som du skapat med Virtual PC eller Virtual Server i

  7. Anonymous says:

    Convertire una macchina Hyper-V in VMware

  8. Thank Yuhong. Appreciate the clarification.



  9. Morthorst – no, I’ve never heard of that (MOSS/WSS going TO Hyper-V). Can you provide a pointer to something for me to investigate?  The other way back can be problematic as I discussed above. I would recommend if that is required to keep a backup of the original VHD and configuration under Virtual PC/Virtual Server.



  10. Anonymous says:

    Hyper-V HW & SW requirement: Hyper-V RTM

  11. Anonymous says:

    Nous voici donc à la troisième étape de notre prise en main d’Hyper-V sur une configuration

  12. Anonymous says:

    下面的内容,是由微软全球技术中心工程师收集和整理的虚拟化技术资料集锦。基本上涵盖了学习和应用基于Hyper-V架构的虚拟化平台所需要掌握的知识和资料。非常的有价值。 1 .Hyper-V的安装部署 在Windows

  13. Gareth – not that I’m aware of.



  14. Anonymous says:

    Honestly I was shocked when I read John’s recent post about " Are VHDs compatible between Hyper-V

  15. Lee – as much as this *may* work, please note that it would not be supported.



  16. Anthony – I’m not on the VMM team, but (IIRC), you can use VMM2007 to P2V into a virtual machine under Virtual Server.

    You can convert from VS to Hyper-V using the steps documented at



  17. Joel Chambers says:

    I hope that this compatibility issue can be updated to include the ability to remove the "Integration Components" from any state of Hyper-V virtual machine so it could be installed on a MS Virtual PC (2004-2007) or MS Virtual Server 2005 R2 version; once it gets out of Beta.

    As I am on the subject of dream requests, being able to support conversions from Physical to Vitual with a seemless tool like VMware’s "Converter" utility would be a lot less painful than the Microsoft route.

    Oh and heck, why not ask for a solution only the uterly insane might request, compatibiliy with actual VMware virtual machine files; or perhaps a means to convert VMDK to VHD integrated into the non-Beta version of Hyper-V?

    One can always dream.

  18. Chris Beckett says:

    Even the straight migration back and forth between Virtual PC 2007 and Hyper-V does not really work. I have a MOSS development environment running under Virtual PC 2007 with Office 2007, etc. When I boot it under Hyper-V it tells me the hardware has changed significantly and that I have to re-activate Windows. This is also true of SharePoint Designer 2007 and possibly other Microsoft applications. Having to re-activate the OS and Office apps every time you boot it between VPC2007 and Hyper-V does not seem like a reasonable option to me?

  19. says:


    I made W2003 R2 SP2 Std Edt 32bit VM under Virtual Server 2005 R2 SP1, migrated VHD to Hyper-V, installed Integration Services, created new machine, et voila! It worked well.

    Then I was asked to move it back to Virtual Server 2005 R2 SP1. I’ve tried with Uninstalation of Intergation services, but didn’t work. Then I mounted VHD as drive letter and replaced HAL.DLL with old one. IT WORKS !!!!

  20. MrGroove says:

    I appreciate the article.  I’ve just posted a recent How-To on the conversion side.  Hope this helps.

  21. Morthorst says:

    Any news of coverting from Hyper-V to Virtual Server an Virtual PC? I have developers needing this possibility from time to time? I have heard that converting x86 VHDs with WSS or MOSS (SharePoint) could give problems, any comment’s on that one and I would appreciate it?

  22. Yuhong Bao says:

    "I guess that some Linux flavours with appropriate boot switches may be OK, but I’m no expert in this area."

    Linux do not use HALs and instead include code for all combinations in the kernel, thus it should always work.

  23. Yuhong Bao says:

    "In theory it is possible to swap the HAL, but not in a Microsoft supported manner (except on Vista and Windows Server 2008 – that’s a post for another day)."

    You basically go to Device Manager and use Update Driver and change the HAL to "ACPI PC" or "Standard PC".

  24. Anthony says:

    What if I have a server running Server 2003 32 bit, and I use Virtual Machine Manager 2007 (because VMM2008 doesn’t run on 32bit) to convert the physical server to a virtual server, then install Server 2008 on another server and run the Server 2003 vhd file as a VM in Hyper-V.  Will that work?

  25. Scott Wilson says:

    Does anyone know how to go from Xen server to Hyper-V? looking for a solution that will not cost alot.


  26. Gareth Marshall says:

    Would it be possible to switch from Hyper-V to Virtual PC by booting off the OS installation CD and doing some kind of repair?

  27. Lee Mitchell says:

    If you copy the hal and ntoskrnl from c:windowsservicepackfilesi386 into c:windowssystem32 (back up the originals first) then you should be able to move from hyper-v to virtual server.

    (This is theoretical, I haven’t done it in this scenario but when converting p2v I have had to do this so that the generic hal is in place that will allow it to boot so I’m pretty confident it will work. If it doesn’t and you get a non-booting machine, attach the vhd to a working virtual machine as an extra disk and restore the backed up hal and ntoskrnl).

  28. Gihan Karunatilake says:

    Great Article!

Comments are closed.

Skip to main content