From: Fam Zheng <famz@redhat.com>
To: Lutz Vieweg <lvml@5t9.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] I/O errors reported to guest for raw-image-file backed /dev/vda - but host sees no I/O errors
Date: Wed, 20 Apr 2016 10:11:01 +0800 [thread overview]
Message-ID: <20160420021101.GC8684@ad-mail.usersys.redhat.com> (raw)
In-Reply-To: <nf5r01$klb$1@ger.gmane.org>
On Tue, 04/19 19:47, Lutz Vieweg wrote:
> The guest drive parameters are:
> > -drive "file=image.raw,if=virtio,format=raw,media=disk,cache=unsafe,werror=report,rerror=report"
Given this implies aio=threads...
> Can you provide any hint on how to pursue the cause of these errors?
> (I thought about using "strace -f -p ..." on qemu, but I don't
> know what exactly to look for in the output - some failed "pwrite()"
> to the image file?)
... yes, this should work.
Fam
next prev parent reply other threads:[~2016-04-20 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 17:47 [Qemu-devel] I/O errors reported to guest for raw-image-file backed /dev/vda - but host sees no I/O errors Lutz Vieweg
2016-04-20 2:11 ` Fam Zheng [this message]
2016-04-20 11:50 ` Kevin Wolf
2016-04-20 14:38 ` Lutz Vieweg
2016-04-21 15:54 ` Lutz Vieweg
2016-04-22 1:16 ` Fam Zheng
2016-04-22 10:47 ` Lutz Vieweg
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=20160420021101.GC8684@ad-mail.usersys.redhat.com \
--to=famz@redhat.com \
--cc=lvml@5t9.de \
--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).