From: Antoine Martin <antoine@nagafix.co.uk>
To: Avi Kivity <avi@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
kvm@vger.kernel.org
Subject: Re: raw disks no longer work in latest kvm (kvm-88 was fine)
Date: Mon, 08 Mar 2010 02:25:08 +0700 [thread overview]
Message-ID: <4B93FD94.7060508@nagafix.co.uk> (raw)
In-Reply-To: <4B93FBC1.3000209@redhat.com>
On 03/08/2010 02:17 AM, Avi Kivity wrote:
> On 03/07/2010 09:13 PM, Antoine Martin wrote:
>>> What version of glibc do you have installed?
>>
>> Latest stable:
>> sys-devel/gcc-4.3.4
>> sys-libs/glibc-2.10.1-r1
>>
>
> $ git show glibc-2.10~108 | head
> commit e109c6124fe121618e42ba882e2a0af6e97b8efc
> Author: Ulrich Drepper <drepper@redhat.com>
> Date: Fri Apr 3 19:57:16 2009 +0000
>
> * misc/Makefile (routines): Add preadv, preadv64, pwritev, pwritev64.
>
> * misc/Versions: Export preadv, preadv64, pwritev, pwritev64 for
> GLIBC_2.10.
> * misc/sys/uio.h: Declare preadv, preadv64, pwritev, pwritev64.
> * sysdeps/unix/sysv/linux/kernel-features.h: Add entries for
> preadv
>
> You might get away with rebuilding glibc against the 2.6.33 headers.
>
The latest kernel headers available in gentoo (and they're masked unstable):
sys-kernel/linux-headers-2.6.32
So I think I will just keep using Christoph's patch until .33 hits portage.
Unless there's any reason not to? I would rather keep my system "clean".
I can try it though, if that helps you clear things up?
next prev parent reply other threads:[~2010-03-07 19:25 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 20:48 raw disks no longer work in latest kvm (kvm-88 was fine) Antoine Martin
2010-03-06 21:28 ` Michael Tokarev
2010-03-07 4:14 ` Antoine Martin
2010-03-07 9:32 ` Michael Tokarev
2010-03-07 10:00 ` Christoph Hellwig
2010-03-07 13:12 ` Antoine Martin
2010-03-07 13:52 ` Antoine Martin
2010-03-07 15:15 ` Michael Tokarev
2010-03-07 17:11 ` Antoine Martin
2010-03-07 17:18 ` Avi Kivity
2010-03-07 17:21 ` Christoph Hellwig
2010-03-07 17:30 ` Avi Kivity
2010-03-07 17:34 ` Christoph Hellwig
2010-03-07 18:43 ` raw disks no longer work in latest kvm (kvm-88 was fine) [SOLVED] Antoine Martin
2010-03-07 18:55 ` Avi Kivity
2010-03-07 18:01 ` raw disks no longer work in latest kvm (kvm-88 was fine) Antoine Martin
2010-03-07 18:47 ` Avi Kivity
2010-03-07 19:07 ` Antoine Martin
2010-03-07 19:10 ` Avi Kivity
2010-03-07 19:13 ` Antoine Martin
2010-03-07 19:17 ` Avi Kivity
2010-03-07 19:25 ` Antoine Martin [this message]
2010-03-07 19:35 ` Avi Kivity
2010-03-13 9:51 ` Antoine Martin
2010-03-14 7:34 ` Avi Kivity
2010-04-08 22:00 ` Antoine Martin
2010-05-22 10:44 ` Antoine Martin
2010-05-22 11:17 ` Michael Tokarev
2010-05-22 11:35 ` Antoine Martin
2010-05-23 8:53 ` Antoine Martin
2010-05-23 11:57 ` Avi Kivity
2010-05-23 14:07 ` Antoine Martin
2010-05-23 14:18 ` Avi Kivity
2010-05-23 14:43 ` Antoine Martin
2010-05-23 14:53 ` Antoine Martin
2010-05-23 14:56 ` Avi Kivity
2010-05-23 15:06 ` Antoine Martin
2010-05-23 15:12 ` Avi Kivity
2010-05-23 16:18 ` Antoine Martin
2010-05-23 17:47 ` Stefan Hajnoczi
2010-05-29 9:42 ` Antoine Martin
2010-05-29 9:55 ` Stefan Hajnoczi
2010-05-29 10:34 ` Christoph Hellwig
2010-05-29 11:06 ` Stefan Hajnoczi
2010-05-29 10:34 ` Christoph Hellwig
2010-03-07 19:09 ` Asdo
2010-03-07 19:11 ` Antoine Martin
2010-03-07 19:12 ` Avi Kivity
2010-03-07 16:21 ` Avi Kivity
2010-03-08 16:45 ` Anthony Liguori
2010-03-07 9:36 ` Gleb Natapov
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=4B93FD94.7060508@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--cc=avi@redhat.com \
--cc=hch@infradead.org \
--cc=kvm@vger.kernel.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).