From: Avi Kivity <avi@qumranet.com>
To: "Anoosh Hosseini (anoosh)" <anoosh@cisco.com>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: kvm-70 + RHEL4 + 2.6.25.7 == invalid module format
Date: Sun, 22 Jun 2008 10:08:42 +0300 [thread overview]
Message-ID: <485DFA7A.1030206@qumranet.com> (raw)
In-Reply-To: <8575A1BA6D8006418FD2CD73FCC2B2E6068C693D@xmb-sjc-231.amer.cisco.com>
(re-adding kvm@)
Anoosh Hosseini (anoosh) wrote:
> BTW I see this issue with kvm-69. But not in kvm-68. Right now use
> kvm-68's kvm-intel module along with kvm-69 simulation. Works fine.
> -anoosh
>
I don't think anything special happened between kvm-68 and kvm-69. This
might be a toolchain problem. Is your gcc/binutils toolchain completely
updated?
If it is, can you try bisecting to see which commit introduced the problem?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2008-06-22 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 19:15 kvm-70 + RHEL4 + 2.6.25.7 == invalid module format Anoosh Hosseini (anoosh)
2008-06-22 6:08 ` Avi Kivity
2008-06-22 6:27 ` Anoosh Hosseini (anoosh)
[not found] ` <8575A1BA6D8006418FD2CD73FCC2B2E6068C693D@xmb-sjc-231.amer.cisco.com>
2008-06-22 7:08 ` Avi Kivity [this message]
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=485DFA7A.1030206@qumranet.com \
--to=avi@qumranet.com \
--cc=anoosh@cisco.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