From: Chris Webb <chris@arachsys.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Richard Davies <richard@arachsys.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Zhi Yong Wu <wuzhy@cn.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] ide: convert pio code path to asynchronous I/O
Date: Thu, 29 Mar 2012 17:10:17 +0100 [thread overview]
Message-ID: <20120329161016.GT5511@arachsys.com> (raw)
In-Reply-To: <CAJSP0QUQew15ZDWD=qZ6d4gXYTExE0M8GH7A8sHUL02WxC1twA@mail.gmail.com>
Stefan Hajnoczi <stefanha@gmail.com> writes:
> Thanks for trying it out.
>
> Regarding the guest kernel errors, they may be timeouts. The guest
> may consider the IDE controller buggy/dead due to how long requests
> take to complete under severe throttling. There's not much that can
> be done about that, I think. If you think the guest errors are due to
> something else though, please post the error messages.
I'm sure you're right that they're standard timeouts. We see exactly the
same behaviour when a guest is on a very heavily contended disk with slow
access because of that.
Best wishes,
Chris.
prev parent reply other threads:[~2012-03-29 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 15:43 [Qemu-devel] [PATCH 0/2] ide: convert pio code path to asynchronous I/O Stefan Hajnoczi
2012-03-28 15:43 ` [Qemu-devel] [PATCH 1/2] ide: convert ide_sector_read() " Stefan Hajnoczi
2012-03-29 6:42 ` Michael Tokarev
2012-03-29 8:29 ` Stefan Hajnoczi
2012-03-29 9:10 ` Paolo Bonzini
2012-03-29 6:46 ` Michael Tokarev
2012-03-29 7:00 ` Michael Tokarev
2012-03-28 15:43 ` [Qemu-devel] [PATCH 2/2] ide: convert ide_sector_write() " Stefan Hajnoczi
2012-03-28 15:51 ` [Qemu-devel] [PATCH 0/2] ide: convert pio code path " Chris Webb
2012-03-28 16:14 ` Paolo Bonzini
2012-03-29 2:15 ` Zhi Yong Wu
2012-03-29 11:30 ` Chris Webb
2012-03-29 13:36 ` Stefan Hajnoczi
2012-03-29 16:10 ` Chris Webb [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=20120329161016.GT5511@arachsys.com \
--to=chris@arachsys.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard@arachsys.com \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.com \
--cc=wuzhy@cn.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.