This is currently a known issue, but specifically when dealing with VMs. We have seen this behavior with both VMware VMs and Hyper-V guests as well. In this situation, the workaround is to load the SDC at the Hypervisor level and carve up LUNs for the guests that way.  This behavior does not happen with the SDC loaded on bare metal hardware. If the above mirrors your scenario, please follow the above procedure to have those guests use the ScaleIO storage. If you are seeing this behavior with bare metal hardware, please open a service request.  There will be some changes made to the ScaleIO support matrix in the new few weeks regarding RHEL/CentOS 7.4 and it's supportability. Essentially, it will state the above info, that it will be supported on bare-metal hardware, but is not supported at the VM level. We are currently tracking down where the issue resides.  Thanks!
Hi everyone,  I've recently added my first CentOS 7.4 SDC to one of my ScaleIO clusters. However, as soon as I map a volume to the SDC, it freezes, goes 100% CPU and just plain dies.  Have anyone seen this issue before?  I have tested this on both SDC/SDS version 2.0.1.3 and 2.0.1.4. 
ScaleIO 2.0.1.4 + Centos7.4 SDC