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.
-Taylor Brown
-Program Manager, Hyper-V
-http://blogs.msdn.com/taylorb
This is something I cannot do with MS Learning VM's. There must be an easy solution to import older formats to the newer versions of Hyper-V.
There are 10 type of people. Those who understand binary and those who do not.
My Blog |
Hire Me
Janos, have you found your way of importing MS Learning VMs? They seem to be missing an .xml-file that is needed for import, only the .exp-file... By loading them to a "middle-station" (Server 2012) I can during the import create the needed .xml-file, but
that tripples the job needed to import the Machines.
Mostly greatful if you have some experience to share.
Joel
