Description of problem: The behaviour and the concept of Vm pinning is causing confusion both in usage and development and affects related parts of the application like: HA, CPU pining, Pin-to-host, PCI-passthrough etc. We need to define the behaviour and interactions of Pin-To-Host, Migration Options, Run, Run-Once, and Migrate and their part in the implementation. On top of that, The UI doesn't reflect the mix of behaviour e.g it is not clear what is going to happen when choosing assigning a Host to a Vm to run on, with combinations of Migration Options, and have the Hosts being unavailable.
*** This bug has been marked as a duplicate of bug 1254818 ***