Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi, for sure there is no such thing as 'automatic migration of VM2 when VM1 is migrated' I am not 100% sure, but I think that migration or evacuation will fail for either VM1 or VM2 in case you will not specify target Compute Host. Unless you work on some release earlier than ~Kilo the policies are hard policies, so affinity will be forced (but it will not take effect in case you specify target hypervisor- that will override scheduler) To make it worse I think it will fail also in case you attempt to migrate/evacuate them simultaneously.

The answer to that could be using soft affinity/anti-affinity, supported from Mitaka