From: Matteo Frigo <athena@fftw.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU/KVM SCSI lock up
Date: Wed, 02 Apr 2008 20:41:24 -0400 [thread overview]
Message-ID: <87k5jfixcb.fsf@fftw.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
kvm-64 hangs under heavy disk I/O with scsi disks. To reproduce,
create a fresh qcow2 disk, boot linux, and execute
dd if=/dev/sdX of=/dev/null bs=1M
on the fresh disk. See also https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1895893&group_id=180599
I have attached a patch that appears to fix the problem. The bug
seems to be the following. scsi_read_data() does the following
bdrv_aio_read()
r->sector += n;
r->sector_count -= n;
For reasons that I do not fully understand, bdrv_aio_read() does
not return immediately, but instead it calls scsi_read_data()
recursively. Since ``r->sector += n;'' has not been executed
yet, the re-entrant call triggers a read of the same sector, which
breaks the producer-consumer lockstep. The fix is to swap the operations
as follows:
r->sector += n;
r->sector_count -= n;
bdrv_aio_read()
A similar fix applies to scsi_write_data().
Thanks for developing kvm, it is truly an amazing piece of software.
Regards,
Matteo Frigo
[-- Attachment #2: scsi-patch --]
[-- Type: application/octet-stream, Size: 1375 bytes --]
diff -aur kvm-64.old/qemu/hw/scsi-disk.c kvm-64.new/qemu/hw/scsi-disk.c
--- kvm-64.old/qemu/hw/scsi-disk.c 2008-03-26 08:49:35.000000000 -0400
+++ kvm-64.new/qemu/hw/scsi-disk.c 2008-03-30 08:37:25.000000000 -0400
@@ -196,12 +196,12 @@
n = SCSI_DMA_BUF_SIZE / 512;
r->buf_len = n * 512;
- r->aiocb = bdrv_aio_read(s->bdrv, r->sector, r->dma_buf, n,
+ r->sector += n;
+ r->sector_count -= n;
+ r->aiocb = bdrv_aio_read(s->bdrv, r->sector - n, r->dma_buf, n,
scsi_read_complete, r);
if (r->aiocb == NULL)
scsi_command_complete(r, SENSE_HARDWARE_ERROR);
- r->sector += n;
- r->sector_count -= n;
}
static void scsi_write_complete(void * opaque, int ret)
@@ -248,12 +248,12 @@
BADF("Data transfer already in progress\n");
n = r->buf_len / 512;
if (n) {
- r->aiocb = bdrv_aio_write(s->bdrv, r->sector, r->dma_buf, n,
+ r->sector += n;
+ r->sector_count -= n;
+ r->aiocb = bdrv_aio_write(s->bdrv, r->sector - n, r->dma_buf, n,
scsi_write_complete, r);
if (r->aiocb == NULL)
scsi_command_complete(r, SENSE_HARDWARE_ERROR);
- r->sector += n;
- r->sector_count -= n;
} else {
/* Invoke completion routine to fetch data from host. */
scsi_write_complete(r, 0);
next reply other threads:[~2008-04-03 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 0:41 Matteo Frigo [this message]
2008-04-03 8:38 ` [Qemu-devel] QEMU/KVM SCSI lock up Avi Kivity
2008-04-03 11:18 ` Matteo Frigo
2008-04-03 11:49 ` Avi Kivity
2008-04-03 11:31 ` Jamie Lokier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k5jfixcb.fsf@fftw.org \
--to=athena@fftw.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).