public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: "Anoosh Hosseini (anoosh)" <anoosh@cisco.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-70 + RHEL4 + 2.6.25.7 == invalid module  format
Date: Sun, 22 Jun 2008 09:08:47 +0300	[thread overview]
Message-ID: <485DEC6F.7050406@qumranet.com> (raw)
In-Reply-To: <8575A1BA6D8006418FD2CD73FCC2B2E6068C68C5@xmb-sjc-231.amer.cisco.com>

Anoosh Hosseini (anoosh) wrote:
> Using RHEL4 base with up-to-date kernel from kernel.org. (enabled
> virtio/kvm..). Checked makefiles and I am building with -mcmodel=kernel.
> Any advise appreciated.
>  
> [root@dell-002 src]# modprobe kvm-intel
> FATAL: Error inserting kvm_intel
> (/lib/modules/2.6.25.7/extra/kvm-intel.ko): Invalid module format
> [root@dell-002 src]# tail /var/log/messages
>
> tail /var/log/messages
> Jun 21 11:56:50 dell-002 kernel: overflow in relocation type 10 val
> ffffffff8829c0d3
> Jun 21 11:56:50 dell-002 kernel: overflow in relocation type 10 val
> ffffffff8829c0d3
> Jun 21 11:56:50 dell-002 kernel: `kvm_intel' likely not compiled with
> -mcmodel=kernel
> Jun 21 11:56:50 dell-002 kernel: `kvm_intel' likely not compiled with
> -mcmodel=kernel
>   

What's the output of 'file /lib/modules/2.6.25.7/extra/kvm-intel.ko'?

Please post host .config.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2008-06-22  6: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 [this message]
2008-06-22  6:27   ` Anoosh Hosseini (anoosh)
     [not found]   ` <8575A1BA6D8006418FD2CD73FCC2B2E6068C693D@xmb-sjc-231.amer.cisco.com>
2008-06-22  7:08     ` Avi Kivity

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=485DEC6F.7050406@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