Server 2022 Datacenter- Hyper-V resets maximum live migrations to 1 after reboot

Question

We have 11 node Hyper-V failover cluster build on windows server 2022 Datacenter. When I change live migrations limit from 1-5 after rebooting the host it get back to 1. I changed it from Hyper-V manager also from PowerShell but the same .

Are we missing a cluster settings that does this for us?

Answer 1

Hello Giorgi,

This setting is configured cluster wide after Sep 2022 CU's. Use following PS to configure it.

(Get-Cluster).MaximumParallelMigrations = 5

Best regards,

Vegard

Answer 2

Hello Giorgi,

Thank you for your question and for reaching out with your question today.

If the live migrations limit in your Hyper-V failover cluster is not persisting after rebooting the host, there are a few things you can check:

1. Ensure that the Cluster Shared Volume settings are properly configured. Open the Failover Cluster Manager, go to the cluster name, and select "Properties." Under the "CSV" tab, check if the "Enable simultaneous live migration" option is selected. If not, enable it and try changing the live migrations limit again.
2. Check if there are any Group Policies in place that override the live migrations limit setting. Group Policies can be set at the cluster level, node level, or OU level. Use the Group Policy Management console to search for policies that might affect the live migration settings and adjust them accordingly.
3. Look for any PowerShell scripts or scheduled tasks that run during startup or periodically and might be resetting the live migrations limit to a specific value. Review any automation or configuration management scripts that could be modifying the Hyper-V settings.
4. Check the cluster configuration file to see if it contains any settings related to live migrations. The cluster configuration file is stored in the cluster storage and can be accessed using the Get-ClusterResource PowerShell cmdlet.
5. If you have Hyper-V Replica configured, ensure that the replica settings are not conflicting with the live migration settings. Check the replica settings in Hyper-V Manager and verify that they are not overriding the live migration limit.
6. Ensure that the Hyper-V Integration Services on all cluster nodes are up to date. Outdated integration services could potentially cause issues with live migration settings.

I’ve used Chat GPT to formulate part of this response. I’ve verified that the solution is accurate before sharing it here with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.