From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Heads up: glibc preadv emulation breaks qemu on older kernels
Date: Thu, 11 Feb 2010 19:06:08 +0000 [thread overview]
Message-ID: <20100211190608.GA26410@amd.home.annexia.org> (raw)
This isn't a problem with qemu as such, but it may affect you if you
use qemu with a newer glibc on a Linux kernel which does not support
the preadv(2) syscall natively. glibc will attempt to emulate
preadv(2) using pread(2) syscalls, but it doesn't align the user
buffer when it does this, and that can break things (if using
cache=off then the file is opened with O_DIRECT which has strict
alignment requirements).
The user visible effect of this bug is that blocks devices (of all
types) inside the guest throw large numbers of I/O errors.
https://bugzilla.redhat.com/show_bug.cgi?id=563103#c8
One interesting thing is that qemu has its own preadv emulation (which
does the emulation correctly), but this is never used because qemu
never gets ENOSYS back from preadv.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
next reply other threads:[~2010-02-11 19:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 19:06 Richard W.M. Jones [this message]
2010-02-12 12:52 ` [Qemu-devel] Heads up: glibc preadv emulation breaks qemu on older kernels Christoph Hellwig
2010-02-12 13:49 ` malc
2010-02-12 13:50 ` Christoph Hellwig
2010-02-12 17:28 ` Anthony Liguori
2010-02-12 18:47 ` Richard W.M. Jones
2010-02-15 22:17 ` Christoph Hellwig
2010-02-15 22:20 ` Richard W.M. Jones
2010-02-12 18:58 ` Avi Kivity
2010-02-15 22:16 ` Christoph Hellwig
2010-02-16 10:41 ` Avi Kivity
2010-02-16 10:45 ` Richard W.M. Jones
2010-02-12 13:56 ` Jamie Lokier
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=20100211190608.GA26410@amd.home.annexia.org \
--to=rjones@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).