Live Migration works with Failover Cluster Manager but not VMM

I have two Server 2008 R2 Datacenter systems setup in a failover cluster using CSV with the Hyper-V role added. I recently setup System Center Virtual Machine Manager R2 to manage this Hyper-V cluster. When I try to "migrate" a running Guest VM using VMM I get "Error 10698 Virtual Machine XXXX could not be live migrated to Virtual Machine Host YYYY using this cluster configuration. 0x80004005." When I stop the Guest VM and migrate it works without errors. Strangely enough when I use the Failover Cluster Management tool on one of the nodes both Quick and Live Migration work without any problems.

Also, when using VMM and clicking "Migrate" I don't get to choose between Quick or Live. VMM seems to be choosing for me and I can't see any way to change it. I am not even sure what kind of migration it is using on a stopped VM because it just says "Cluster" in the Transfer Type column.

Another strange behavior is that even though both of the nodes in my failover cluster are exactly the same I get an error message that a Guest VM can not be migrated because it is "using processor specific features" not supported on the other node. Checking the "allow migration to a virtual machine host with a different processor" check box on the Guest VM settings clears up this issue but I would still like to know what is going on here.
System EngineerSystems EngineerAsked:
Who is Participating?
 
System EngineerSystems EngineerAuthor Commented:
Any idea what a "Cluster" migration might be? Does VMM ever use a Quick Migration?

I stumbled across the solution to my problem of VMM not being able to Live Migrate. I was attempting to use VMM on a cluster where I had just added a node that was a mirror image of my first node and all it took was the "Microsoft Silver Bullet" otherwise known as rebooting to clear up the issue.
0
 
r_panosCommented:
I forgot to mention that migration of VMs in Windows Server 2008 R2 Hyper-V, managed by SCVMM "008 R2 are Live Migrations:

"...When you migrate a running virtual machine within a cluster created in Windows Server 2008 R2 Hyper-V and managed by using VMM 2008 R2, VMM performs a live migration. With live migration, you can move running virtual machines from one Hyper-V physical host to another without any interruption of service or perceived service outage. If you have not upgraded to Windows Server 2008 R2, for migrations within a Windows Server 2008 cluster, VMM performs a quick migration, with a brief interruption of service and no loss of state that is in memory while the virtual machine is migrated<!--[if gte mso 9]>   Normal  0          false  false  false    EN-US  X-NONE  X-NONE                                                                          <![endif]--><!--[if gte mso 9]>                                                                                                                                                                                                                                                                                    <![endif]--><!--[if gte mso 10]><![endif]-->When you migrate a running virtual machine within acluster created in Windows Server 2008 R2 Hyper-V and managed byusing VMM 2008 R2, VMM performs a live migration.With live migration, you can move running virtual machines from one Hyper-Vphysical host to another without any interruption of service or perceivedservice outage. If you have not upgraded to Windows Server 2008 R2,for migrations within a Windows Server 2008 cluster, VMM performs a quickmigration, with a brief interruption of service and noloss of state that is in memory while the virtual machine is migrated..."

This is from page 160 of VMM08R2_Operations.docx that can be found in http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=e547b676-112f-419e-8d8f-6920beca0845
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
r_panosCommented:
Sorry copying the reference messed it up :-(
0
 
gtworekCommented:
Are your host CPUs _identical_ in both nodes?
0
 
System EngineerSystems EngineerAuthor Commented:
Yes, they are both Dell PowerEdge 2950's with Intel Xeon E5410 @ 2.33GHz.
0
 
gtworekCommented:
Did your cluster pass validation during creating?
Did you try to disable all unused NICs on hosts?
Do you have plenty of free RAM and HDD space when you try to migrate?
0
 
System EngineerSystems EngineerAuthor Commented:
Cluster validation passed with only a couple of warnings because I have multiple network adapters on the same subnet.

I have plenty of free RAM and HDD space. This is going to eventually be our production Hyper-V system so I over-engineered all of the hardware.
0
 
gtworekCommented:
Looks for me like some strange networking issue but I have no idea what actually happens.
I guess you cannot separate network subnets for your interfaces?

I played with such configuration many times and it just works...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.