From: John Snow <jsnow@redhat.com>
To: Dongli Zhang <dongli.zhang@oracle.com>, qemu-devel@nongnu.org
Cc: Qemu-block <qemu-block@nongnu.org>, Marc Olson <marcolso@amazon.com>
Subject: Re: [Qemu-devel] How to emulate block I/O timeout on qemu side?
Date: Fri, 2 Nov 2018 13:49:25 -0400 [thread overview]
Message-ID: <ad9227ab-bcce-1703-e6aa-a7b14907868b@redhat.com> (raw)
In-Reply-To: <ae2d0fbd-5198-47e8-9ad2-40a85f0b3576@default>
On 11/02/2018 04:11 AM, Dongli Zhang wrote:
> Hi,
>
> Is there any way to emulate I/O timeout on qemu side (not fault injection in VM
> kernel) without modifying qemu source code?
>
> For instance, I would like to observe/study/debug the I/O timeout handling of
> nvme, scsi, virtio-blk (not supported) of VM kernel.
>
> Is there a way to trigger this on purpose on qemu side?
>
> Thank you very much!
>
> Dongli Zhang
>
I don't think the blkdebug driver supports arbitrary delays right now.
Maybe we could augment it to do so?
(I thought someone already had, but maybe it wasn't merged?)
Aha, here:
https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg05297.html
V2: https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg00394.html
Let's work from there.
--js
next prev parent reply other threads:[~2018-11-02 17:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 8:11 [Qemu-devel] How to emulate block I/O timeout on qemu side? Dongli Zhang
2018-11-02 17:49 ` John Snow [this message]
2018-11-02 17:55 ` Marc Olson
2018-11-02 18:17 ` John Snow
2018-11-03 17:24 ` Dongli Zhang
2018-11-05 17:13 ` John Snow
2018-11-12 7:13 ` Marc Olson
2018-11-12 7:36 ` Dongli Zhang
2018-11-12 22:52 ` Marc Olson
2018-11-13 0:31 ` Dongli Zhang
2018-11-05 17:49 ` Eric Blake
2018-11-06 6:17 ` Dongli Zhang
2018-11-06 9:14 ` [Qemu-devel] [Libguestfs] " Richard W.M. Jones
2018-11-06 9:43 ` Richard W.M. Jones
2018-11-06 15:52 ` Richard W.M. Jones
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=ad9227ab-bcce-1703-e6aa-a7b14907868b@redhat.com \
--to=jsnow@redhat.com \
--cc=dongli.zhang@oracle.com \
--cc=marcolso@amazon.com \
--cc=qemu-block@nongnu.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).