VM creation fails with 'blk_cloned_rq_check_limits' errors

Issue

• Getting blk_cloned_rq_check_limits errors while creating a VM in RHV:

  kernel: blk_update_request: critical target error, dev dm-31, sector 1454376940 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0
  kernel: blk_update_request: critical target error, dev dm-31, sector 1456211920 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0
  kernel: blk_update_request: critical target error, dev dm-31, sector 1453328380 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0
  kernel: device-mapper: multipath: Failing path 65:224.
  kernel: device-mapper: multipath: Failing path 8:64.
  kernel: blk_cloned_rq_check_limits: over max size limit. (65535 > 0)
  multipath[2735244]: dm-31: no usable paths found
  multipathd[2900]: sde: mark as failed
  multipathd[2900]: 360010ead0878abc1234567890: remaining active paths: 1
  multipathd[2900]: sdae: mark as failed
  multipathd[2900]: 360010ead0878abc1234567890: Entering recovery mode: max_retries=4
  multipathd[2900]: 360010ead0878abc1234567890: remaining active paths: 0
  [...]
  multipathd[2900]: 360010ead0878abc1234567890: sde - tur checker reports path is up
  kernel: device-mapper: multipath: Reinstating path 8:64.
  multipathd[2900]: 8:64: reinstated
  multipathd[2900]: 360010ead0878abc1234567890: queue_if_no_path enabled
  multipathd[2900]: 360010ead0878abc1234567890: Recovered to normal mode
  multipathd[2900]: 360010ead0878abc1234567890: remaining active paths: 1
  kernel: blk_cloned_rq_check_limits: over max size limit. (65535 > 0)
  kernel: device-mapper: multipath: Failing path 8:64.
  kernel: blk_cloned_rq_check_limits: over max size limit. (65535 > 0)
  kernel: blk_cloned_rq_check_limits: over max size limit. (65535 > 0)
  [...]