Created attachment 1728783 [details] Screenshot showing that SCSI Pass-Through enabled by default Description of problem: When creating a new Direct LUN disk, "SCSI Pass-Through" is enabled by default. SCSI Pass-Through is needed only in special cases, is not supported properly by multipath (see bug 1854659, bug 1855868, bug 1860377) and it does not provide the best performance. As a general rule, RHV defaults should give the simplest, most reliable, and best performance out of the box. Features that are not common or may decrease reliability or performance should be enabled by a user only if needed. This gives the best user experience and minimize support cost. Version-Release number of selected component (if applicable): 4.4.4.1_master How reproducible: Always Steps to Reproduce: 1. Create new vm or edit an existing vm 2. Create new Direct LUN disk Actual results: Enable SCSI Pass-Through is checked Expected results: Enable SCSI Pass-Through is not checked Additional info: The issue with SCSI Pass-Through and multiapth is explained by bug 1854659. oVirt does not have any mechanism to resume VMs using Direct LUN disks so VM paused because of failed ioctl are never resumed automatically. Direct LUN disks not using SCSI Pass-Through are less likely to get paused because of ioctl failure. When creating a floating Direct LUN disk, SCSI Pass-Through is not enabled by default. The issue exist only when creating attached disk.
Benny, do we have the same issue with MBS disks?
(In reply to Nir Soffer from comment #1) > Benny, do we have the same issue with MBS disks? No, we currently do not have the option to enable it (not in the GUI at least)
Verified on ovirt-engine-4.4.5.2-0.1.el8ev. When creating a new VM or editing an existing VM and creating a new Direct LUN disk, 'Enable SCSI Pass-Through' is not checked as expected. Moving to VERIFIED.
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.