Importing SERVER2008R2 Hyperv virtual machines on SERVER2012R2

Importing Windows R2 Hyper-V VM into Windows 8.1

For the purposes of this post, let's try and import a VM called ad1hc1.  This is successfully exported from Windows Server R2 Hyper-V.  Currently this VM and all its associated files reside in the G:\VMs\AD1HC1 folder. The various files can be seen here:

There is no hidden tricks and it is a exported VM that can being imported to Windows Server R2 without issues, and H As been many times.

If we use the GUI and try to import the VMS into Windows 8.1

We get the following error:

Hyper-V did not find virtual machines to import from location ' G:\VMs\AD1HC1 '

When reviewing-what-Process Monitor sees on the file system, there is no Access Denied error messages. We are able to read the disk and review the files contained within.

If the files exist on the disk and we can read them. For the eagle eyed out there, you may be wondering why the. exp file have not been read ....

Digging in

If you wrote scripts to Import/export Windows Server for Hyper-V VMs, there is a small clue in the Hyper-V section locate   D in the Features removed or Deprecated in Windows Server page on TechNet. **

• VM Chimney (also called TCP offload) has been removed. The TCP chimney is not being available to guest operating systems.
• Support for Static VMQ have been removed. Drivers using NDIS 6.3 would automatically access Dynamic VMQ capabilities that is new in Windows Server 2012.

• The WMI root\virtualization namespace is deprecated. The new namespace is root\virtualization\v2.

• Windows Authorization Manager (AzMan) is deprecated. Need to use new management tools for virtual machines or redesign the authorization model.

And if we then look at the same sections in the Features removed or Deprecated in Windows Server R2

• WMI root\virtualization Namespace v1 (used in Hyper-V)

So the WMI v1 namespace is deprecated in Windows Server, and then removed in Windows Server, R2.  Why are this important?  When the export is made to export the VM from Windows R2, the WMI v1 namespace is used. This can is seen with a PowerShell snippet which binds to the Hyper-V WMI Namespace.

$VMManagementService = Get-wmiobject-namespace Root\virtualization-class Msvm_virtualsystemmanagementservice- ComputerName $HyperVHost

In a post on the Hyper-V TechNet Forum There is some details worth reading from Taylor Brown, and if you don ' t already re The ad his blog, the RSS feed is here.

VM ' s that is exported from Windows Server R2 utilized the version 1 WMI namespace which resulted in an. exp File to represent the exported virtual machine. In Windows Server we introduced a new WMI namespace (version 2 or ROOT\VIRTUALIZATION\V2) which implemented a much be Tter Import/export model–allowing Effectively just copy the virtual machine folder (with the VM ' s XML configurati On file inside it) as well as the VM's VHDs and then import that directly. For Windows Server maintained, the version 1 WMI namespace which allowed for importing of Windows Server 2008/R2 VMS ' s on 2012.

In Windows Server R2 we have removed the old version 1 namespace which means we can ' t import virtual machines that WH ere exported from Windows Server 2008/r2.

What does

As you can see, VMs this were exported from Windows Server & R2 cannot is imported As-is into Windo WS-Server R2 or Windows 8.1.

Don ' t Panic Captain Mainwaring, don ' t panic! ***

Don ' t panic as there is options!!  Let's look at them based on the scenario. There is both basic takes on this:

1. Original Hyper-V Server and the VM is still available
2. Original Hyper-V Server is not available

Original Hyper-V Server & VMs Available

If you exported from Windows Server or R2, and the original host is a still available with the VMs then probably T He easiest option would be to get the VMs off this machine in a format that's easily importable to Hyper-V- R2.

On the original Hyper-V server, power down the VMs.  Once they has shut down and then stop the Hyper-V Virtual machine Management Service (VMMS).  This would unlock the VMs ' files.  Simply copy over the VM folders to the Windows server, R2 server and they can be imported. Remember This is one of the features added to Windows Server 2012-we does not has to specifically export a VM before it  can be imported. Funnily enough this functionality is added in the WMI V2 namespace for Hyper-V ....

Original Hyper-V Server unavailable

If the original server or a copy of the VMs is no longer available, there is still a couple of options. This is the scenario if you is re-purposing the hardware and the original machine have been wiped, or if these are arc hived Lab VMs is trying to import to a new version of Hyper-V.

Perform Intermediate Import

If, and this won't apply to everyone, you have a Windows Server (Hyper-V machine), the 2008/2008 R2 VMs can be imp  Orted to that server. Note that this is a R2 server.  Since still has the WMI v1 namespace (albeit deprecated), we can import the. Exp machines.  Once successfully imported to +, the VMs can be exported or copied on to Windows Server for R2. You don't need to power on the VMs after importing them to the intermediate Windows server, which server is O Nly used to perform the import thus allowing the VM to is copied to Windows Server,R2.

Travis mentioned an interesting take on the the comments below.  Consider a temporary boot to VHD option just to get the necessary import step is done.  Thanks travis! Would love to know if-helps folks out at All–please Post a comment below!

Update 2-12-2013: Added A How to on this topic. Please refer to this post.

Create New vm–reuse Virtual Hard Disk

If the above method is not available, or is too time consuming, a option is to create new VM configuration and specify to  Use a existing virtual hard disk.  By doing so we can re-use the VM's virtual hard disk file. Since the virtual NIC now have a different GUID Windows would recognise it as a different NIC, and you'll need to re-enter The IP address in the VM.

from:http://blogs.technet.com/b/rmilne/archive/2013/10/22/ windows-hyper-v-2012-amp-8-1-hyper-v-did-not-find-virtual-machine-to-import.aspx?pageindex=2

https://social.microsoft.com/Forums/zh-CN/b283169a-eb9b-4140-87f1-ac3a8b3e174c/server2012r2server2008r2hyperv?forum=2222

Importing SERVER2008R2 Hyperv virtual machines on SERVER2012R2