From: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
To: Avi Kivity <avi@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: kvm-87 fails to compile under uClibc
Date: Wed, 08 Jul 2009 19:59:21 +0300 [thread overview]
Message-ID: <1247072361.13629.15.camel@localhost.localdomain> (raw)
In-Reply-To: <4A5334FC.50100@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]
On Tue, 2009-07-07 at 14:43 +0300, Avi Kivity wrote:
> On 07/07/2009 02:31 PM, Cristi Magherusan wrote:
> > 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?
> >
>
> I think 2.6.24 is too old for current qemu-kvm. Also it doesn't receive
> security fixes; if you don't trust your users you should use 2.6.27.y or
> 2.6.30.y (or a vendor kernel).
Hi Avi,
Thanks for this advice, I'll switch to 2.6, whch should be ok since it's
also supported by OpenVZ.
> You can reduce qemu size by not compiling tcg; that'll save you a lot
> more than the kernel.
How do I disable it? is it the --disable-cpu-emulation configure flag?
Unfortunately that one breaks compilation, and I reproduced this both in
my system and inside the buildroot toolchain that I'm using.
--
Ing. Cristi Măgherușan, System/Network Engineer
Technical University of Cluj-Napoca, Romania
http://cc.utcluj.ro +40264 401247
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-08 16:59 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 [this message]
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
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=1247072361.13629.15.camel@localhost.localdomain \
--to=cristi.magherusan@net.utcluj.ro \
--cc=avi@redhat.com \
--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