1 2 Previous Next 20 Replies Latest reply on Aug 11, 2010 12:19 PM by tuique

    vsock module won't insmod on Ubuntu 8.10 (intrepid)

    stevemaring Novice














      while installing 64-bit VMware Server 2.0.0 build-116503 on 64-bit Ubuntu 8.10 (intrepid) I get problems with vsock module ... everything else seems to be fine






      Building the vsock module.


      Using 2.6.x kernel build system.

      make: Entering directory `/tmp/vmware-config0/vsock-only'

      make -C /lib/modules/2.6.27-4-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

      make[1]: Entering directory `/usr/src/linux-headers-2.6.27-4-generic'

      CC   /tmp/vmware-config0/vsock-only/linux/af_vsock.o

      CC   /tmp/vmware-config0/vsock-only/linux/driverLog.o

      CC   /tmp/vmware-config0/vsock-only/linux/util.o

      /tmp/vmware-config0/vsock-only/linux/util.c: In function ‘VSockVmciLogPkt’:

      /tmp/vmware-config0/vsock-only/linux/util.c:157: warning: format not a string literal and no format arguments

      CC   /tmp/vmware-config0/vsock-only/linux/vsockAddr.o

      LD   /tmp/vmware-config0/vsock-only/vsock.o

      Building modules, stage 2.

      MODPOST 1 modules

      WARNING: "VMCIDatagram_CreateHnd" /tmp/vmware-config0/vsock-only/vsock.ko undefined!

      WARNING: "VMCIDatagram_DestroyHnd" /tmp/vmware-config0/vsock-only/vsock.ko undefined!

      WARNING: "VMCI_GetContextID" /tmp/vmware-config0/vsock-only/vsock.ko undefined!

      WARNING: "VMCIDatagram_Send" /tmp/vmware-config0/vsock-only/vsock.ko undefined!

      CC      /tmp/vmware-config0/vsock-only/vsock.mod.o

      LD   /tmp/vmware-config0/vsock-only/vsock.ko

      make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-4-generic'

      cp -f vsock.ko ./../vsock.o

      make: Leaving directory `/tmp/vmware-config0/vsock-only'

      Unable to make a vsock module that can be loaded in the running kernel:

      insmod: error inserting '/tmp/vmware-config0/vsock.o': -1 Unknown symbol in module

      There is probably a slight difference in the kernel configuration between the

      set of C header files you specified and your running kernel.  You may want to

      rebuild a kernel based on that directory, or specify another directory.









      -Steve Maring



        1 2 Previous Next