On Mon, 2011-12-05 at 18:29 +0100, Paolo Bonzini wrote: > The virtio-scsi HBA is the basis of an alternative storage stack > for QEMU-based virtual machines (including KVM). Could you clarify what the problem with virtio-blk is? > Compared to > virtio-blk it is more scalable, because it supports many LUNs > on a single PCI slot), This is just multiplexing, surely, which should be easily fixable in virtio-blk? > more powerful (it more easily supports > passthrough of host devices to the guest) I assume this means exclusive passthrough? In which case, why doesn't passing the host block queue through to the guest just work? That means the host is doing all the SCSI back end stuff and you've just got a lightweight queue pass through. > and more easily > extensible (new SCSI features implemented by QEMU should not > require updating the driver in the guest). I don't really understand this comment at all: The block protocol is far simpler than SCSI, but includes SG_IO, which can encapsulate all of the SCSI features ... I'm not familiar necessarily with the problems of QEMU devices, but surely it can unwrap the SG_IO transport generically rather than having to emulate on a per feature basis? James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
