As far as it goes for RHEV:
- Virtual machine migration will fail if migrating from a hypervisor with SELinux enabled to one with SELinux disabled
- A virtual machine previously started on a hypervisor with SELinux enabled will not start on a hypervisor with SELinux disable.
RHEV manages the SELinux configuration on RHEV Hypervisors in a persistent state, SELinux is enabled by default.
You'll need to run sestatus as a superuser on each host in the cluster and observe the output,
evaluate each host in the cluster to make sure the setting for "SELinux status" is consistent.
Regards,