From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
=?ISO-8859-15?Q?Andreas_F=E4?=@gnu.org,
rber <andreas.faerber@web.de>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] kvm: Improve upgrade notes when facing unsupported kernels
Date: Sun, 07 Jun 2009 12:38:39 +0300 [thread overview]
Message-ID: <4A2B8A9F.4060709@redhat.com> (raw)
In-Reply-To: <4A2B88B1.4060005@web.de>
Jan Kiszka wrote:
> Users complained that it is not obvious what to do when kvm refuses to
> build or run due to an unsupported host kernel, so let's improve the
> hints.
>
> diff --git a/configure b/configure
> index 42d46f2..8ccb58c 100755
> --- a/configure
> +++ b/configure
> @@ -1158,7 +1158,9 @@ EOF
> | grep "error: " \
> | awk -F "error: " '{if (NR>1) printf(", "); printf("%s",$2);}'`
> if test "$kvmerr" != "" ; then
> - kvm="no - (${kvmerr})"
> + kvm="no - (${kvmerr})\n\
> + NOTE: To enable KVM support, update your kernel to 2.6.29+ or install \
> +recent kvm-kmod from http://sourceforge.net/projects/kvm."
> fi
>
Installing kvm-mod is insufficient, you need the headers from somewhere.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-06-07 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 9:30 [Qemu-devel] [PATCH] kvm: Improve upgrade notes when facing unsupported kernels Jan Kiszka
2009-06-07 9:38 ` Avi Kivity [this message]
2009-06-07 9:40 ` [Qemu-devel] " Jan Kiszka
2009-06-07 9:45 ` Avi Kivity
2009-06-07 9:51 ` Jan Kiszka
2009-06-07 9:53 ` Avi Kivity
2009-06-07 9:57 ` Jan Kiszka
2009-06-07 10:07 ` Avi Kivity
2009-06-07 13:47 ` Blue Swirl
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=4A2B8A9F.4060709@redhat.com \
--to=avi@redhat.com \
--cc==?ISO-8859-15?Q?Andreas_F=E4?=@gnu.org \
--cc=andreas.faerber@web.de \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@web.de \
--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).