(Apologies for not noticing this earlier in the development cycle;
I have been on leave and am just getting back.)

A colleague of mine noticed an inability to start a guest with the
2.11 RC's, when a vhost-scsi device is defined in the guest.  The
symptoms on s390 are an exception loop in the guest, which is ugly:

[    1.006087] Kernel stack overflow.
[    1.006145] CPU: 1 PID: 114 Comm: systemd-udevd Not tainted 4.4.0-83-generic #106-Ubuntu
[    1.006237] task: 000000000165d7c0 ti: 0000000001474000 task.ti: 0000000001474000
[    1.006331] Krnl PSW : 0704d00180000000 00000000001f8bd0 (search_module_extables+0x68/0xc0)
[    1.006453]            R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 EA:3
Krnl GPRS: a42be0ffd90b3c69 0000000000000000 0000000000bd8ce0 0000000000000000
[    1.006627]            00000000001f8bd0 00000000001f0ff8 0000000000000000 0000000000000000
[    1.006693]            0704d00180000000 00000000001f8bd0 00000000000000e0 fffffffffffffff8
[    1.006786]            00000000001f8bd0 00000000007d8b38 00000000014740a8 0000000001474078
[    1.006886] Krnl Code: 00000000001f8bbe: c020004f0091        larl    %r2,bd8ce0
           00000000001f8bc4: ecb1fff800d9       aghik   %r11,%r1,-8
          #00000000001f8bca: ec1200268064       cgrj    %r1,%r2,8,1f8c16
          >00000000001f8bd0: d503d000b000       clc     0(4,%r13),0(%r11)
           00000000001f8bd6: a784fff1           brc     8,1f8bb8
           00000000001f8bda: e330b1740012       lt      %r3,372(%r11)
           00000000001f8be0: a784ffec           brc     8,1f8bb8
           00000000001f8be4: ec331dbc0355       risbg   %r3,%r3,29,188,3
[    1.007385] Call Trace:
[    1.007416] ([<00000000014740c8>] 0x14740c8)
[    1.007477]  [<000000000012205c>] do_no_context+0x34/0xf8
[    1.007528]  [<00000000007c2328>] pgm_check_handler+0x15c/0x1a4
[    1.007590]  [<00000000001f8bd0>] search_module_extables+0x68/0xc0
[    1.007661] ([<0000000001474270>] 0x1474270)
[    1.007725]  [<000000000012205c>] do_no_context+0x34/0xf8
[    1.007789]  [<00000000007c2328>] pgm_check_handler+0x15c/0x1a4
[    1.007865]  [<00000000001f8bd0>] search_module_extables+0x68/0xc0
[    1.007929] ([<0000000001474418>] 0x1474418)
...repeating...

Since this worked perfectly fine with 2.10, I was able to bisect the
problem to commit 5c0919d02066 ("virtio-scsi: Add virtqueue_size parameter
allowing virtqueue size to be set.").  When I attempted to revert this
commit from 2.11-rc3, I get a build error because commit 920036106044
("vhost-user-scsi: add missing virtqueue_size param") makes no sense.

This made the problem rather straightforward, because the change that
was put in for vhost-user-scsi needed to also be added for vhost-scsi.

I haven't looked at the vhost-user-scsi stuff to know how it works and/or
whether we could combine matters into VhostSCSICommon (or whatever).  If
there were more time before 2.11 I would, but thought this would be a
better solution in the short term.

Eric Farman (1):
  vhost-scsi: add missing virtqueue_size parameter

 hw/scsi/vhost-scsi.c | 2 ++
 1 file changed, 2 insertions(+)

-- 
2.13.5