From: Dongli Zhang <dongli.zhang@oracle.com>
To: Eric Blake <eblake@redhat.com>, jsnow@redhat.com
Cc: qemu-devel@nongnu.org, libguestfs <libguestfs@redhat.com>
Subject: Re: [Qemu-devel] How to emulate block I/O timeout on qemu side?
Date: Tue, 6 Nov 2018 14:17:46 +0800 [thread overview]
Message-ID: <fef3b167-0d69-d61d-418b-535fb6d36dfc@oracle.com> (raw)
In-Reply-To: <bd913c1b-fcbe-b198-3955-4b4b2e33757a@redhat.com>
On 11/06/2018 01:49 AM, Eric Blake wrote:
> On 11/2/18 3: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?
>
> You may be interested in Rich's work on nbdkit. If you don't mind the overhead
> of the host connecting through NBD, then you can use nbdkit's delay and
> fault-injection filters for inserting delays or even run-time-controllable
> failures to investigate how the guest reacts to those situations
Thank you all very much for the suggestions. I will take a look on nbdkit.
So far I am reproducing the issue with NFS (by shutdown the link to NFS where
the image is placed on purpose) but it did not work well.
>
>>
>> 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
>>
>>
>
Dongli Zhang
next prev parent reply other threads:[~2018-11-06 6:16 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
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 [this message]
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=fef3b167-0d69-d61d-418b-535fb6d36dfc@oracle.com \
--to=dongli.zhang@oracle.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=libguestfs@redhat.com \
--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).