From: Avi Kivity <avi@redhat.com>
To: antoni artigues <tartigues@iac3.eu>
Cc: kvm@vger.kernel.org
Subject: Re: compilation problem
Date: Wed, 26 Jan 2011 14:53:34 +0200 [thread overview]
Message-ID: <4D40194E.5010401@redhat.com> (raw)
In-Reply-To: <1296041839.2391.21.camel@dalia.intranet.iac3.eu>
On 01/26/2011 01:37 PM, antoni artigues wrote:
> Hello
>
> Well, we have a 32 nodes cluster. With RHEL4 and 2.6.9 kernel in all the
> nodes. The cluster is in production. Now, is not possible to update each
> of the 32 nodes.
>
> We want to use opennebula with KVM in the cluster. So, we are trying to
> compile the kvm-kmod.
>
> Is not possible? Do we need to update the kernel of each node?
A new kernel is needed. Note the RHEL 6 kernel includes kvm, so you
don't need to compile anything. Of course, if the cluster is in
production, you'll need to plan this carefully.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-01-26 12:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 10:48 compilation problem antoni artigues
2011-01-26 11:17 ` Avi Kivity
2011-01-26 11:37 ` antoni artigues
2011-01-26 12:53 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-24 1:12 Niklas Molin
2014-01-23 22:06 Niklas Molin
2014-01-23 22:12 ` Gary Thomas
2010-05-31 14:54 Onkar Mahajan
2008-08-19 13:16 Compilation problem Kevin Hickey
2008-08-19 13:27 ` Martin Michlmayr
2008-08-19 16:06 ` Ralf Baechle
2008-07-10 8:58 Compilation Problem Chris Calitz
2008-07-11 21:30 ` Bob Copeland
2008-07-11 23:37 ` Luis R. Rodriguez
2006-12-08 11:46 Compilation problem PUCCETTI Armand
2006-12-08 11:17 ` Steven Hand
2006-12-08 16:23 ` PUCCETTI Armand
2005-05-19 6:25 compilation problem Wieslaw Faruga
2005-05-19 6:25 ` Jean Delvare
2003-08-30 10:28 Martchukov Anton
2003-08-30 12:30 ` Mark Frey
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=4D40194E.5010401@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=tartigues@iac3.eu \
/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.