KB: A live migration of a non-clustered virtual machine in Virtual Machine Manager fails with error 0x8007274D

KB: A live migration of a non-clustered virtual machine in Virtual Machine Manager fails with error 0x8007274D

  • Comments 7
  • Likes

KB533443333Just a quick FYI on a new Knowledge Base article we published today. This one talks about an issue where an attempt to perform a live migration on non-clustered virtual machines (shared nothing live migration) from one host to another will show a zero rating for the desired host and display the following text in the Rating Explanation field:

Migration check for virtual machine <serverName> failed to create a planned virtual machine in the target host.  Detailed error message: The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host serverName.contoso.com: No connection could be made because the target machine actively refused it. (Ox8007274D).

You can get all of the details in the article below:

KB2853203 - A live migration of a non-clustered virtual machine in Virtual Machine Manager fails with error 0x8007274D (http://support.microsoft.com/kb/2853203)

J.C. Hornbeck | Knowledge Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • There seems to be a problem with  audio and driviing in safe mode  oops drivers  RESOLUTION PLEASE

  • I have problem with shared nothing migration between cluster when using VMM2012 SP1, will the scenario be the same when to try moving a HA VM between cluster1 (win 2012) to cluster2 (win 2012) if specific live migration network is configured for the clusters, the live migration subnet is same for both cluster, but the VMM server doesn´t have any IP configured on the LM network.

  • @Olle - You'll have the same issue because the VMM server doesn´t have any IP configured on the LM network. We'll look to update the KB clarify the additional scenarios.

    DeWitt

  • @DeWitt Hurst [MSFT] Thanks for Quick response, yes I can confirm that´s the reason why my migration failed in my specific case. In the KB that solution should be: "to add LM network also to VMM", don´t know if this is possible or wanted in all scenarios. In my specific scenario I just added also the management network for LM and the migration worked as expected. Guess I need to rethink my network design.

  • Adding a network card to VMM server, connected to the LM subnet is not solving the problem in my case.

    I can ping both Hyper-V servers through the LM interface from VMM server but the LM still fails with the same message. Any ideas?

  • Same problem as 'jackito'. So far the only solution is a private DNS server on the LM network.

    The lookup occurs then it returns with the public ip address instead of the private ip address on which vmms.exe isn't listening...or that's how I get it.

    Thanks.

  • So.... does this mean that there will be fix coming out for this?  In my case, my two hosts are 40 miles away from the VMM Management server, and there is no way for me to plug it into the private network.