public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Andreas Hasenack <ahasenack-y7mWNqJcIDpfJ/NunPodnw@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: error modprobing
Date: Mon, 26 Feb 2007 12:23:00 +0200	[thread overview]
Message-ID: <45E2B504.1000407@qumranet.com> (raw)
In-Reply-To: <200702260719.28511.ahasenack-y7mWNqJcIDpfJ/NunPodnw@public.gmane.org>

Andreas Hasenack wrote:
> On Monday 26 February 2007 03:39:28 Avi Kivity wrote:
>   
>> richard lucassen wrote:
>>     
>>> Kernel: 2.6.20.1
>>> kvm-15
>>> AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
>>> 1G memory
>>>
>>> After modprobing kvm-amd, the system becomes very very unstable and I
>>> have to reboot te get things right (after modprobing kvm-amd e.g. the
>>> ssh daemon is unaccessible)
>>>
>>> Here's stdout from the compile session:
>>>
>>> http://www.xaq.nl/kvm/index.html
>>>       
>> dmesg says the modprobe failed, and then the internal filesystem used by
>> kvm was not unregistered.  a subsequent read of /proc/filesystems failed.
>>
>> I'll look into it.  Thanks for the report.
>>     
>
>
> Same here with kvm-intel. I get an oops a few seconds later when doing 
> something that would stat the mounted filesystems (like installing an rpm).
>
>   

Looks like two separate issues:

- the kvm-15 tarball inadvertently ships kernel/*.mod.c files, which 
break the build.  Try removing these files (and kernel/*.o for good 
measure) and rebuilding.
- there's probably a missing unregister_filesystem() or a close relative 
on some error path.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
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-02-26 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25 21:16 error modprobing richard lucassen
     [not found] ` <20070225221645.3adc491b.mailinglists-+AO6ZX++/Fdg9hUCZPvPmw@public.gmane.org>
2007-02-26  6:39   ` Avi Kivity
     [not found]     ` <45E280A0.8050803-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-26 10:19       ` Andreas Hasenack
     [not found]         ` <200702260719.28511.ahasenack-y7mWNqJcIDpfJ/NunPodnw@public.gmane.org>
2007-02-26 10:23           ` Avi Kivity [this message]
2007-02-26 14:34   ` Avi Kivity
     [not found]     ` <45E2EFDE.2000807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-28 15:52       ` Andreas Hasenack

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=45E2B504.1000407@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=ahasenack-y7mWNqJcIDpfJ/NunPodnw@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