So you are planning to configure VM-VM anti-affinity policy in your AHV environment to ensure critical VMs run on different hosts. That’s thoughtful thinking right there and it makes sense.
Now if you create this policy when the VMs are off... when you power them on, you’ll see the policy kick in and the VMs will be running on different hosts.
But… what if the VMs were powered on when you applied the policy? Do you have to restart the VMs?
The answer is No.
After the policy is created, Acropolis Dynamic Scheduling (ADS) will migrate the VMs running on the same hosts to different ones.
This will not happen immediately though. It takes a while for ADS to start migrating these VMs.
So sit relaxed, you created the policy… ADS will take care of it.
Want to know how to configure VM-VM anti-affinity policy or how to delete it. Check it out here
Have any questions? Drop a comment and let's start a discussion.