I am sure everyone is now trying out Windows 2012 R2. I am also doing the same
Just want to share some information on the export and import between different versions of Hyper-V
|SOURCE HYPERV||DESTINATION HYPERV||CAN IMPORT ?|
|WINDOWS 2008||WINDOWS 2012 R2||NO|
|WINDOWS 2008 R2||WINDOWS 2012 R2||NO|
|WINDOWS 2012||WINDOWS 2012 R2||YES|
|WINDOWS 2012 R2||WINDOWS 2012||NO|
However, there is a workaround mentioned on Technet Forum by Taylor Brown (MSFT) on making the import getting worked from Windows 2008 R2 to Windows 2012 R2.
VM’s that are exported from Windows Server 2008 or 2008 R2 utilized the version 1 WMI namespace which resulted in a .exp file to represent the exported virtual machine. In Windows Server 2012 we introduced a new WMI namespace (version 2 or root\virtualization\v2) which implemented a much better import/export model – allowing you to effectively just copy the virtual machine folder (with the VM’s XML configuration file inside it) as well as the VM’s VHDs and then import that directly. For Windows Server 2012 we maintained the version 1 WMI namespace which allowed for importing of Windows Server 2008/R2 VM’s on 2012.
In Windows Server 2012 R2 we have removed the old version 1 namespace which means we can’t import virtual machines that where exported from Windows Server 2008/R2. However we can import them if you copy the virtual machine xml file and VHD’s – to do this you need to stop the vmms on the 2008/R2 server – copy all of the virtual machine files/vhds to the Windows Server 2012 R2 server and then import them.
My first production cluster will be up tomorrow with Windows 2012 R2. I wish if the option for exporting back to Windows 2012 was there. That would give high confidence for an early adapters.
Cheers and good luck !