From: Kevin Wolf <kwolf@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v0 0/5]: BLOCK_IO_ERROR QMP event
Date: Wed, 03 Feb 2010 11:25:13 +0100 [thread overview]
Message-ID: <4B694F09.2020903@redhat.com> (raw)
In-Reply-To: <1265145013-23231-1-git-send-email-lcapitulino@redhat.com>
Am 02.02.2010 22:10, schrieb Luiz Capitulino:
> Hi,
>
> This series adds the BLOCK_IO_ERROR event libvirt guys have requested,
> I have made some improvements after Kevin's feedback and hope it's in better
> shape now.
>
> The only small issue is that I couldn't get a read error. I've followed Kevin's
> advices wrt NFS, but got only write errors...
I should have explained in more detail what I'm doing to produce a read
error... I boot the system from a local image that won't go away when
NFS is down. I add another image (can be empty) stored on NFS and with
cache=off. Then I turn NFS off and start something like a dd if=/dev/vdb
of=/dev/null iflag=direct. This way you produce only reads.
Kevin
prev parent reply other threads:[~2010-02-03 10:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 21:10 [Qemu-devel] [PATCH v0 0/5]: BLOCK_IO_ERROR QMP event Luiz Capitulino
2010-02-02 21:10 ` [Qemu-devel] [PATCH 1/5] QMP: BLOCK_IO_ERROR event handling Luiz Capitulino
2010-02-03 9:18 ` [Qemu-devel] " Kevin Wolf
2010-02-03 11:27 ` Luiz Capitulino
2010-02-02 21:10 ` [Qemu-devel] [PATCH 2/5] block: BLOCK_IO_ERROR QMP event Luiz Capitulino
2010-02-02 21:10 ` [Qemu-devel] [PATCH 3/5] ide: Generate " Luiz Capitulino
2010-02-03 8:31 ` Christoph Hellwig
2010-02-03 9:10 ` Kevin Wolf
2010-02-03 11:41 ` Luiz Capitulino
2010-02-02 21:10 ` [Qemu-devel] [PATCH 4/5] scsi: " Luiz Capitulino
2010-02-02 21:10 ` [Qemu-devel] [PATCH 5/5] virtio-blk: " Luiz Capitulino
2010-02-03 10:25 ` Kevin Wolf [this message]
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=4B694F09.2020903@redhat.com \
--to=kwolf@redhat.com \
--cc=lcapitulino@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).