I dont think QEMU scsi emulation supports WRITE_VERIFY. In the past there was a few instances where the code in the SCSI emulation that determines the transfer direction, based on the opcode, did not contain a new opcode, so it got the xfer direction wrong and crashed.
I dont have access to my box with QEMU right now, but I would check if it is something similar to this patch : http://lists.gnu.org/archive/html/qemu-devel/2012-04/msg04130.html regards ronnie sahlberg On Mon, Apr 8, 2013 at 8:53 AM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > On Fri, Apr 05, 2013 at 11:30:00AM -0700, Venkatesh Srinivas wrote: >> When a Linux guest does a simple 'sg_verify /dev/<scsi disk on a >> virtio-scsi HBA>', qemu (-master from git) crashes, tripping an >> assertion in scsi-disk.c:scsi_dma_complete(), that the completing DMA >> command has no IOCB. >> >> The callpath is: >> scsi_dma_complete >> dma_complete >> dma_bdrv_cb >> dma_bdrv_io >> dma_bdrv_read >> scsi_do_read >> bdrv_co_em_bh >> aio_bh_poll >> aio_poll. >> >> At the assertion, we have a zero-element iovector and the request has >> a status of -1. > > CCing Paolo Bonzini and Asias He. See the ./MAINTAINERS file to find > people that can help with specific QEMU subsystems. > > It would be nice to include a full gdb backtrace when possible since > that may include extra information like that value of arguments in the > call stack. > > Stefan >
