public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg M Lee <Greg.Lee-CM8Ft84HMKulVyrhU4qvOw@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: strange error loading kvm module on latest FC6	kernel
Date: Wed, 07 Mar 2007 21:42:02 +1300	[thread overview]
Message-ID: <1173256922.4343.7.camel@greg-linux.ncs.co.nz> (raw)
In-Reply-To: <45EE62F6.3060300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Hi
  thanks for that. It fixed that problem, but now I get:

# modprobe kvm-intel
FATAL: Error inserting kvm_intel
(/lib/modules/2.6.19-1.2911.6.5.fc6/extra/kvm-intel.ko): Operation not
supported

and dmesg has:
kvm: disabled by bios

I have a Compaq nw8440 which I ordered with the thought of installing
Xen (unfortunately I found Xen 3.0 too "clunky"). I went into ROM BIOS
and couldn't find any related option, the nearest being:  Core Duo:
enabled/disabled.  So I guess that I am out of luck :-(

Late news - found a bios update that claims that it adds an option to
enable VT. will try tomorrow and report back.

-Greg

On Wed, 2007-03-07 at 09:00 +0200, Avi Kivity wrote:
> Greg M Lee wrote:
> > Hi
> >   updated to latest FC6 kernel yesterday ie 2.6.19-1.2911.6.5.fc6
> > compiled kvm-15 from sourceforge this morning
> > chose the unpatched kernel instructions [ was this the right choice ?]
> > configure, make, make install all went fine (some warnings here and
> > there)
> > modprobe kvm-intel gave a bunch of errors in dmesg the first of which
> > was:  SELinux: initialized (dev kvmfs, type kvmfs), not configured for
> > labeling
> >
> >   
> 
> Ouch.  Anybody here know how to deal with that?
> 
> > so I disabled SELinux
> > modprobe kvm-intel still gave a bunch of errors in dmesg:
> >
> > kvm_intel: Unknown symbol gfn_to_memslot
> >   
> 
> Try with the attached patch.  Unfortunately you also have to reboot.
> 


-------------------------------------------------------------------------
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-03-07  8:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07  4:28 strange error loading kvm module on latest FC6 kernel Greg M Lee
     [not found] ` <1173241719.4317.5.camel-nqhUBgQlnDodtexkPab+ZEgmxNRb6L7S@public.gmane.org>
2007-03-07  7:00   ` Avi Kivity
     [not found]     ` <45EE62F6.3060300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-07  8:42       ` Greg M Lee [this message]
2007-03-07 15:34       ` James Morris
2007-03-08 13:37         ` Daniel J Walsh
     [not found]           ` <1173361148.10467.30.camel@moss-spartans.epoch.ncsc.mil>
     [not found]             ` <1173361148.10467.30.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2007-03-08 13:52               ` Avi Kivity
2007-03-08 16:38               ` Daniel J Walsh

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=1173256922.4343.7.camel@greg-linux.ncs.co.nz \
    --to=greg.lee-cm8ft84hmkulvyrhu4qvow@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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