From: Jan Kiszka <jan.kiszka@web.de>
To: Bug 494500 <494500@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Bug 494500] Re: QEMU 0.12.0 does not support KVM with Kernel < 2.6.29, bug in ./configure and kvm-all.c
Date: Thu, 01 Jul 2010 09:04:29 +0200 [thread overview]
Message-ID: <4C2C3DFD.5010408@web.de> (raw)
In-Reply-To: <20100630130541.18635.51520.malone@wampee.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
rowa wrote:
> Does the _lastest_ kvm-kmod's install the right headers for the used
> kernel, for example kernel 2.6.28-11?
It installs the headers required to build kvm support into the qemu that
allows full-featured kernel or kvm-kmod usage up to the version kvm-kmod
carries.
>
> As I wrote in this bug I had problems with a kernel 2.6.28-11 and the
> _latest_ version of kvm-kmod. It works only with the right (not the
> latest) version of kvm-kmod.
Once you properly installed the kernel headers that kvm-kmod delivers,
qemu should detect their presence during configure and succeed with this
step. Of course, you also have to install the kvm-kmod modules which
will disable those that come with 2.6.28 to actually run qemu in kvm
mode later on.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-07-01 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091209132347.795.21673.malonedeb@gangotri.canonical.com>
2010-06-30 11:26 ` [Qemu-devel] [Bug 494500] Re: QEMU 0.12.0 does not support KVM with Kernel < 2.6.29, bug in ./configure and kvm-all.c Jes Sorensen
2010-06-30 11:56 ` rowa
2010-06-30 12:43 ` Iggy
2010-06-30 13:05 ` rowa
2010-07-01 7:04 ` Jan Kiszka [this message]
2010-07-01 9:47 ` [Qemu-devel] " Jes Sorensen
2010-07-12 10:55 ` [Qemu-devel] " rowa
2011-02-20 17:11 ` Aurelien Jarno
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=4C2C3DFD.5010408@web.de \
--to=jan.kiszka@web.de \
--cc=494500@bugs.launchpad.net \
--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 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.