I tried both. When i tried modprobe it says that vhost_net.ko not found. Actually i want to point out that i configured the module to be built along with the linux kernel itself during the make menuconfig. I suppose that building along with the kenrel should take care of all the dependencies, right? Also the module should have been automatically loaded during bootup if it is configured as a module during the kernel build. It didn't do it either. And then when i tried to manually load, i got the unknown symbol error. So i think then it is some mistake in the kernel makefiles, right? Please correct me if i am wrong.
Thanks, Bala On Sat, May 22, 2010 at 8:27 PM, Simon Kitching <[email protected]>wrote: > On Sat, 2010-05-22 at 19:20 -0400, Balachandar wrote: > > Hello, > > I recently downloaded the 2.6.34 kernel and wanted to use the new > > vhost_net module. I selected the option in the 'make menuconfig' as a > > module and built the kernel. After rebooting, i couldn't find the > > module using the lsmod command. So i decided to insert the module > > manually. But when i tried to insert the module i get an error > > 'vhost_net: Unknown symbol tun_get_socket'. So which mailing list > > should i approach to ask them to correct this mistake. > > Did you use the "modprobe" or "insmod" command? > > modprobe will automatically load dependencies, while insmod will not. > > See the manpages for insmod and modprobe for more details. > > Regards, Simon > >
