When attempting to migrate an offline VM from a 2008 R2 Cluster to a 2012 Cluster, the vmmservice.exe process crashes after completing the BITS transfer when starting the actual VM import.
I've been able to reproduce this exact problem in two seperate environments (both my production and test environments). I've also been able to reproduce a similar issue, but when migrating between two non clustered 2012 hosts in my lab.
I'm getting the following error int he application log when the VMM Service crashes:
Log Name: Application
Source: Windows Error Reporting
Date: 2/4/2013 2:21:20 PM
Event ID: 1001
Task Category: None
Fault bucket , type 0
Event Name: VMM20
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: 6f658ebd-6f08-11e2-93ff-b499ba03dc00
Report Status: 4
<Provider Name="Windows Error Reporting" />
<TimeCreated SystemTime="2013-02-04T20:21:20.000000000Z" />
Any assistance will be greatly appreciated.
The information from the log is not to helpful in this thread, but it seams it's related to your virtual networks and/or configuration in the fabric.
Can you please explain the detailed steps you are performing in these operations, so that I can eventually test this on my own and get back to you?.
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )
In short, I have two seperate VMM/Hyper-V environments. Prod and Test. Both are more or less setup the same, with the exception of the number of Hyper-V hosts, and the library config. Prod is using a Windows 2012 File share cluster for the library, where test is running the library off of the VMM Management host.
In both environments I am unable to do a shared nothing migration from a 2008 R2 Hyper-V cluster, to a 2012 Hyper-V cluster.
As for the network error, the best explanation I can find for the network error, is that it is looking for the 'same' switch when it tries to migrate from one cluster to another cluster which obviously does not exist. The 2008 R2 cluster has the default 2008 R2 Hyper-V switch configured, whereas the 2012 Hyper-V cluster is using a Logical Switch.
All Logical Networks, VMNetworks, VLAN's, etc are configured identically between the 2008 R2 cluster and the 2012 cluster.
And before you ask, yes I am powering off the guest prior to attempting a shared nothing migration (This is a requirement when migrating from 2008 -> 2012)