public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Francesc <frank-VfcrZIqfQH54piUD7e9S/g@public.gmane.org>
To: Michael Riepe <michael-0QoEqw4nQxo@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: compiler problem in Read Hat ES 4
Date: Thu, 25 Jan 2007 08:28:57 +0100	[thread overview]
Message-ID: <45B85C39.6040707@si.ct.upc.edu> (raw)
In-Reply-To: <45B74F3B.5080508-0QoEqw4nQxo@public.gmane.org>

Michael Riepe wrote:
> Hi!
>
> Francesc wrote:
>
>   
>> I have install 2.6.19.2 kernel in Red Hat and I have got .ko files at 
>> last !!
>> But it seems if there is a problem when I try to load the module:
>>
>> modprobe kvm-intel
>> FATAL: Error inserting kvm_intel 
>> (/lib/modules/2.6.19.2/extra/kvm-intel.ko): Operation not supported
>>     
>
> Please check the output of dmesg. This usually means that a) kvm isn't
> supported or b) it's disabled by the BIOS.
>
>   
Thank's. You were absolutely right. Virtualization was disbled. I 
enabled it and module seems to load.
The only thing is that I get this message:

kvm: no version for "struct_module" found: kernel tainted.
kvm: msrs: 2

does it mean any trouble?

Frank


-- 
Aquest missatge ha estat analitzat per MailScanner
a la cerca de virus i d'altres continguts perillosos,
i es considera que està net.
For all your IT requirements visit: http://www.transtec.co.uk


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2007-01-25  7:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16 10:02 compiler problem in Read Hat ES 4 Francesc
2007-01-17 10:44 ` Uri Lublin
     [not found]   ` <64F9B87B6B770947A9F8391472E0321603496B05-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-17 12:31     ` Francesc
2007-01-17 12:44       ` Uri Lublin
     [not found]         ` <64F9B87B6B770947A9F8391472E0321603496B06-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-18  8:32           ` Francesc
2007-01-18 12:06             ` Uri Lublin
     [not found]               ` <64F9B87B6B770947A9F8391472E0321603496B09-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-01-24  0:20                 ` Bill Davidsen
2007-01-24 13:41                   ` Uri Lublin
2007-01-24 10:53                 ` Francesc
     [not found]                   ` <45B73AB5.1000000-VfcrZIqfQH54piUD7e9S/g@public.gmane.org>
2007-01-24 12:21                     ` Michael Riepe
     [not found]                       ` <45B74F3B.5080508-0QoEqw4nQxo@public.gmane.org>
2007-01-25  7:28                         ` Francesc [this message]
     [not found]                           ` <45B85C39.6040707-VfcrZIqfQH54piUD7e9S/g@public.gmane.org>
2007-01-25  7:44                             ` Michael Riepe

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=45B85C39.6040707@si.ct.upc.edu \
    --to=frank-vfcrziqfqh54piud7e9s/g@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=michael-0QoEqw4nQxo@public.gmane.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