Uderc programming article aggregator sites

Hypev "automatic start action" not retained after live motion

Advertisement
Hi,
We have a hyper-v cluster of 2 windows 2008 R2SP1 nodes.
We found that the settings we made in the VMs "automatic start action" were reset to "none" after migration between the nodes .
We need to have it maintaned
thanks
Stefano
Advertisement
The best answer: Hi ,
I think there may be something unclear in my previous email. Ok, I will detail it.
If you make a virtual machine high available, the Automatic Start Action will not work after you perform a live migration. Which means the following setting will not be "failovered" to another host.
You should set this via the Cluster Manager by the following setting:
This is what I said:
If you change the configuration of a virtual machine, we recommend that you use the Failover Cluster Manager snap-in to access the virtual machine settings. When you do this, the cluster is updated automatically with the configuration changes. However, if
you make changes to the virtual machine settings from the Hyper-V Manager snap-in, you must update the cluster manually after you make the changes. If the configuration is not refreshed after networking or storage changes are made, a subsequent failover may
not succeed or may succeed but result in the virtual machine being configured incorrectly.
Thanks. Feel free to let me know if anything is unclear.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hi Aaron ,
yes I think there's a misunderstanding about the question .
When you say
"If you make a virtual machine high available, the Automatic Start Action will not work after you perform a live migration. Which means the following setting will not be "failovered" to another host."
you mean that it is supposed to work this way ?
I mean , If you make a VM HA with clustering is it an accepted behaviour that the setting of " automatic start action " ( not the stop action you posted the picture of ) is not maintaned after a live migration even if such setting is made through the failover
cluster manager ?
If you are telling me that this is what it is supposed to work I don't agree , because I wish I can have a way to set a priority in VM startup in the case of complete shutdown/reboot .
Working with vsphere as well this is possible and I thought it was the same with Hyper-v
To solve this problem I had to create a group policy's startup script for the cluster nodes in which I start the VM in the correct order with some timeout .
Thanks
Stefano Colombo