On Sun, Jan 14, 2007 at 07:03:12PM +0800, Jeff Chua wrote: > > On 1/14/07, Adrian Bunk <[EMAIL PROTECTED]> 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 > >> > >Please send the 2.6.20-rc5 .config you saw this with. > > Adrian, > > > Only difference is (without CONFIG_PARAVIRT) ... > > < CONFIG_PARAVIRT=y > --- > ># CONFIG_PARAVIRT is not set > > > Thanks, > Jeff. > > > Here's my .config ... >...
I don't have any illegal modules for testing, but the resulting kernel looks good (and many other of the drivers in your kernel would break if paravirt_ops wasn't exported). Could it be you compiled the module against a CONFIG_PARAVIRT=y tree and tried to use it with a CONFIG_PARAVIRT=n kernel? cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/