mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff Chua" <jeff.chua.linux@gmail.com>
To: "Adrian Bunk" <bunk@stusta.de>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
	"Jan Engelhardt" <jengelh@linux01.gwdg.de>,
	"Andrew Morton" <akpm@osdl.org>,
	"Linus Torvalds" <torvalds@osdl.org>
Subject: Re: Linux v2.6.20-rc5
Date: Sun, 14 Jan 2007 21:46:46 +0800	[thread overview]
Message-ID: <b6a2187b0701140546ne0b95d8q7aff70d93ffabb9@mail.gmail.com> (raw)
In-Reply-To: <20070114125648.GV7469@stusta.de>

On 1/14/07, Adrian Bunk <bunk@stusta.de> wrote:
> On Sun, Jan 14, 2007 at 07:03:12PM +0800, Jeff Chua wrote:
> >
> > On 1/14/07, Adrian Bunk <bunk@stusta.de> wrote:
> > >On Sun, Jan 14, 2007 at 03:38:24PM +0800, Jeff Chua wrote:
> > >>
> > >> setting CONFIG_PARAVIRT=y will return in ...
> > >>
> > >>       vmmon.ko module unknown symbol paravirt_ops

> Could it be you compiled the module against a CONFIG_PARAVIRT=y tree and
> tried to use it with a (CONFIG_PARAVIRT=n kernel?

I recompiled the vmmon module under the new kernel with
CONFIG_PARAVIRT=y. It compiled fine, but when loaded, it gives the
unknown symbol warning. I shalll make it clear that this is not a
kernel issue ... it's just vmware, but I don't know how to fix it, and
needed help from the experts.

Thanks,
Jeff.

  reply	other threads:[~2007-01-14 13:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 11:03 Jeff Chua
2007-01-14 12:56 ` Adrian Bunk
2007-01-14 13:46   ` Jeff Chua [this message]
2007-03-08  8:15     ` albcamus
2007-03-08 15:20       ` Jeff Chua
  -- strict thread matches above, loose matches on Subject: below --
2007-01-13  6:05 Jeff Chua
2007-01-23  3:11 ` Herbert Xu
2007-01-12 19:27 Linus Torvalds
2007-01-12 22:26 ` Andrew Morton
2007-01-13  2:26   ` Nigel Cunningham
2007-01-13  3:36   ` Jeff Chua
2007-01-13  3:44     ` Jeff Chua
2007-01-13 20:23       ` Bill Davidsen
2007-01-13 23:58     ` Segher Boessenkool
2007-01-13  5:01   ` Adrian Bunk
2007-01-13 13:02     ` Jan Engelhardt
2007-01-14  7:38       ` Jeff Chua
2007-01-14  7:43         ` Adrian Bunk

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=b6a2187b0701140546ne0b95d8q7aff70d93ffabb9@mail.gmail.com \
    --to=jeff.chua.linux@gmail.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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
all inboxes | Powered by JetHome®