none
Cluster resource 'Virtual Machine VMNAME' of type 'Virtual Machine' in clustered role 'VMNAME' failed. RRS feed

  • Question

  • Hello!

    I have Hyper-V Failover Cluster with 3 node. 

    NODE1: Windows SRV2016

    NODE2: Windows SRV2016

    NODE3: Windows SRV2019

    There are 30 VMs in failover cluster. I can move VMs with Live Migration to all node except one. The one of the VM can move with Live Migration from NODE2 to NODE 1 and NODE1 to NODE2, but I can't move from NODE1 and NODE2 to NODE3 and I get the following error:

    Event id: 1069

    Cluster resource 'Virtual Machine VMNAME' of type 'Virtual Machine' in clustered role 'VMNAME' failed.

    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

    Event id: 1205

    The Cluster service failed to bring clustered role 'VMNAME' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

    Why should be the problem?

    Thank You.

    Friday, June 14, 2019 12:05 PM

All replies

  • Hi,
    Thanks for your question.
    May I confirm that all VMs can failover from node 1,2 to 3 except the specifc one? If this, we can exclude the network issue between the endpoints.

    Meanwhile, would you check which resource under this VM was offline on the FCM console. We could check if problem resource like disks, IPs or others ocurred an issue, then right click it and Show Critical Events. Or we can check that in the Cluster Events. We need to also check the if dependencies of the offline resource encountered a problem. 

    Here's an article discussed the troubleshooting for Clustered VM live migration failed,
    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd446679(v=ws.10)

    Furthermore, we need to check if host 3 occurred a issue that there's insufficient resource for VMs' workloads, such as high CPU, low memory, not enough space.
    Moreover, also we need to check if this VM's setting configured correctly, failover policy and its self setting for running properly.
    Hope above information can help you. If you have any question or concern, please feel free to let me know.
    Best regards,
    Michael

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, June 17, 2019 6:49 AM
    Moderator
  • Have you tried setting the compatibility mode for the processor of the VM that is having issues live migrating?

    tim

    Monday, June 17, 2019 1:04 PM
  • Hi,

    How are things going on? Was your issue was resolved?

    Please feel free to let me know if you need further assistance.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Tuesday, June 18, 2019 10:03 AM
    Moderator
  • Hi,

    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, June 20, 2019 10:46 AM
    Moderator
  • Hi,

    Was your issue resolved?

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, June 28, 2019 9:13 AM
    Moderator
  • The problem was resolved. A virtual DVD connected to the VM and mounted iso locate on the local C: drive not int he ClusteredStorage. After I removed the virtual DVD, the problem was resolved, and I could move the specified VM to another NODE.
    18 hours 33 minutes ago