Re: [Qemu-devel] virtio-scsi limits

2017-04-18 Thread Richard W.M. Jones
On Tue, Apr 18, 2017 at 06:17:03PM +0100, Richard W.M. Jones wrote: > On Tue, Apr 18, 2017 at 05:30:52PM +0200, Paolo Bonzini wrote: > > > When I changed libguestfs to use LUNs instead of targets (target=0 > > > unit=i), I got a peculiar bug. It looks like there is some kind of > > > race when

Re: [Qemu-devel] virtio-scsi limits

2017-04-18 Thread Richard W.M. Jones
On Tue, Apr 18, 2017 at 05:30:52PM +0200, Paolo Bonzini wrote: > > When I changed libguestfs to use LUNs instead of targets (target=0 > > unit=i), I got a peculiar bug. It looks like there is some kind of > > race when enumerating the device, where /sys is populated before the > > device is

Re: [Qemu-devel] virtio-scsi limits

2017-04-18 Thread Paolo Bonzini
On 18/04/2017 17:24, Richard W.M. Jones wrote: > In libvirt, refers to the virtio-scsi "channel". > The current virtio-scsi driver in qemu has a hard limit of 1 channel, > so you can only use bus="0" (or channel=0). > > Open question: Will this limit ever be increased? No, it's only there

[Qemu-devel] virtio-scsi limits

2017-04-18 Thread Richard W.M. Jones
Hi Paolo, I was looking for documentation on the limits of #controllers, #channels, #targets, #LUNs, #disks in virtio-scsi, and couldn't find any, so I thought I would create that documentation instead. I wonder if you could check that the following is correct information. Also - at the bottom