On Mon, Sep 3, 2018 at 8:01 PM Fabrice Bacchella < fabrice.bacchella(a)orange.fr&gt; wrote: I guess oVirt see them as FCP devices? Are these disks connected to multiple hosts? Please share the output of: vdsm-client Host getDeviceList ... Where do I find the protocol multipath thinks the drives are using ? multipath.conf(5) says: The protocol strings that multipath recognizes are scsi:fcp, scsi:spi, scsi:ssa, scsi:sbp, scsi:srp, scsi:iscsi, scsi:sas, scsi:adt, scsi:ata, scsi:unspec, ccw, cciss, nvme, and undef. The protocol that a path is using can be viewed by running multipathd show paths format "%d %P" So this should work: blacklist_exceptions { protocol "(scsi:fcp|scsi:iscsi|scsi:sas)" } The best way to make this change is to create a dropin conf file, and not touch /etc/multipath.conf, so vdsm will be able to update later. $cat /etc/multipath/conf.d/local.conf blacklist_exceptions { protocol "(scsi:fcp|scsi:iscsi|scsi:sas)" } I hope it works for overriding vdsm configuration, if not, you will need to change /etc/multipath.conf, and mark it as VDSM_PRIVATE like this; $ head -3 /etc/multipath.conf # # VDSM REVISION 1.6 # VDSM PRIVATE Once it works, I suggest to file a bug to support sas disks by default. Nir