From: Mike Frysinger <vapier@gentoo.org>
To: uclibc@uclibc.org
Cc: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>,
Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: kvm-87 fails to compile under uClibc
Date: Tue, 7 Jul 2009 10:34:13 -0400 [thread overview]
Message-ID: <200907071034.14623.vapier@gentoo.org> (raw)
In-Reply-To: <1246966290.32432.24.camel@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]
On Tuesday 07 July 2009 07:31:30 Cristi Magherusan wrote:
> On Tue, 2009-07-07 at 12:12 +0300, Avi Kivity wrote:
> > On 07/07/2009 05:42 AM, Cristi Magherusan wrote:
> > > I'm using linux-2.6.26.8, uClibc-HEAD(linuxthreds, almost complete
> > > setup) and gcc 4.3.3.
> > >
> > > Also, is this kernel version supposed to work with this kvm?
> >
> > Yes.
>
> Actually only the headers are 2.6.26.8, the oldest vesion found in
> buildroot. (I wonder why are older ones being abandoned, since the new
> ones tend to get bigger and bigger.)
upgrade
> The kernel will be 2.6.24 because it's smaller. I know this mismatch may
> not be good, but I have to get to a compromise. The kernel needs to be
> as small as possible (everything should fit in a 4MB BIOS flash), and
> also to support both this version of KVM and OpenVZ at the same time.
> Older KVM versions have terrible buildsystem issues and I gave up trying
> to get them compile in buildroot. I think OpenVZ could work on 2.6.26
> too, but I haven't tried yet.
>
> Could this be a real problem at runtime?
with uClibc, yes
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 134 bytes --]
_______________________________________________
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc
next prev parent reply other threads:[~2009-07-07 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 2:42 kvm-87 fails to compile under uClibc Cristi Magherusan
2009-07-07 3:21 ` Mike Frysinger
2009-07-07 7:34 ` Bernhard Reutner-Fischer
2009-07-07 11:15 ` Cristi Magherusan
2009-07-07 14:33 ` Mike Frysinger
2009-07-07 9:12 ` Avi Kivity
2009-07-07 11:31 ` Cristi Magherusan
2009-07-07 11:43 ` Avi Kivity
2009-07-08 16:59 ` Cristi Magherusan
2009-07-08 17:07 ` Avi Kivity
2009-07-08 17:34 ` Cristi Magherusan
2009-07-09 8:20 ` Avi Kivity
2009-07-09 17:58 ` Cristi Magherusan
2009-07-07 14:34 ` Mike Frysinger [this message]
2009-07-07 15:31 ` Javier Guerra
2009-07-07 15:58 ` Cristi Magherusan
2009-07-08 6:13 ` Natanael Copa
2009-07-08 8:12 ` Cristi Magherusan
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=200907071034.14623.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=Cristi.Magherusan@net.utcluj.ro \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=uclibc@uclibc.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).