Page 1 of 3 123 LastLast
Results 1 to 10 of 86

Thread: VMware server 2 vsock warning

Hybrid View

  1. #1
    Join Date
    Oct 2008
    Beans
    55

    VMware server 2 vsock warning

    Hi,

    Wondering if anyone encountered this vsock warning when installing vmware server 2 on intrepid.

    Code:
    None of the pre-built vsock modules for VMware Server is suitable for your 
    running kernel.  Do you want this program to try to build the vsock module for 
    your system (you need to have a C compiler installed on your system)? [yes] 
    
    Extracting the sources of the vsock module.
    
    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-7-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-headers-2.6.27-7-generic'
      CC [M]  /tmp/vmware-config0/vsock-only/linux/af_vsock.o
      CC [M]  /tmp/vmware-config0/vsock-only/linux/driverLog.o
      CC [M]  /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 [M]  /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
      LD [M]  /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 [M]  /tmp/vmware-config0/vsock-only/vsock.ko
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-7-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.
    
    The VM communication interface socket family is used in conjunction with the VM
    communication interface to provide a new communication path among guests and 
    host.  The rest of this software provided by VMware Server is designed to work 
    independently of this feature.  If you wish to have the VSOCK feature  you can 
    install the driver by running vmware-config.pl again after making sure that 
    gcc, binutils, make and the kernel sources for your running kernel are 
    installed on your machine. These packages are available on your distribution's 
    installation CD.
    [ Press the Enter key to continue.]
    it says i got to make sure gcc,binutils,make and kernel sources for my running kernel are installed.Any advice on how to fix it?

  2. #2
    Join Date
    May 2006
    Location
    Here
    Beans
    24

    Re: VMware server 2 vsock warning

    I get the same error when I am trying to compile vmtools with Ubuntu 8.10. I once found another thread on this virtualization forum but no one replies and the "advice" people give is incorrect, just plain wrong, or they say "just use Ubuntu 8.04." Well, thanks for that lame advice, but I am asking about Ubunutu 8.10 not 8.04. Basically it seems if you want to use VMWare and Ubuntu 8.10 it is not possible to install/compile the vmtools. Too bad, wish more people could help on this or offer suggestions that "work!"

  3. #3
    Join Date
    Jul 2006
    Location
    Nantes, France
    Beans
    39
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: VMware server 2 vsock warning

    I experienced the exact same error with "2.6.27-7-generic #1 SMP ... x86_64 GNU/Linux" and vmware-server 2.0.0-116503.x86_64

    Was installed in Hardy (working) and upgraded yesterday to Intrepid. Trying to solve this since one day. Tried http://kramfs.com/2008/07/13/vmware-...e-vsock-module and http://www.insecure.ws/2008/10/20/vm...nd-kernel-2627 workarounds without success.
    Currently downloading vmware-server 2.0.0-122956.x86_64 to see if this chnage anything.

  4. #4
    Join Date
    Oct 2008
    Beans
    55

    Re: VMware server 2 vsock warning

    i've tried vmware server 2 build 122956 x86 on intrepid following some of the links also but unsuccessful.Seems like there is still no solution for intrepid but am sure people are working it out so we may have to wait patiently.

  5. #5
    Join Date
    Oct 2008
    Beans
    3

    Re: VMware server 2 vsock warning

    I am having same issue after upgrading to intrepid kubuntu. This will probably be a major issue for anyone relying on vmware server 2 for more than just hobby work.

    There is a patch but apparently its only for 1.x http://ubuntu-tutorials.com/2008/11/...627-7-generic/


    VMware server 2 error during install:

    None of the pre-built vsock modules for VMware Server is suitable for your
    running kernel. Do you want this program to try to build the vsock module for
    your system (you need to have a C compiler installed on your system)? [yes]

    Extracting the sources of the vsock module.

    Building the vsock module.

    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config3/vsock-only'
    make -C /lib/modules/2.6.27-7-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-headers-2.6.27-7-generic'
    CC [M] /tmp/vmware-config3/vsock-only/linux/af_vsock.o
    CC [M] /tmp/vmware-config3/vsock-only/linux/driverLog.o
    CC [M] /tmp/vmware-config3/vsock-only/linux/util.o
    /tmp/vmware-config3/vsock-only/linux/util.c: In function ‘VSockVmciLogPkt’:
    /tmp/vmware-config3/vsock-only/linux/util.c:157: warning: format not a string literal and no format arguments
    CC [M] /tmp/vmware-config3/vsock-only/linux/vsockAddr.o
    LD [M] /tmp/vmware-config3/vsock-only/vsock.o
    Building modules, stage 2.
    MODPOST 1 modules
    WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config3/vsock-only/vsock.ko] undefined!
    WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config3/vsock-only/vsock.ko] undefined!
    WARNING: "VMCI_GetContextID" [/tmp/vmware-config3/vsock-only/vsock.ko] undefined!
    WARNING: "VMCIDatagram_Send" [/tmp/vmware-config3/vsock-only/vsock.ko] undefined!
    CC /tmp/vmware-config3/vsock-only/vsock.mod.o
    LD [M] /tmp/vmware-config3/vsock-only/vsock.ko
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-7-generic'
    cp -f vsock.ko ./../vsock.o
    make: Leaving directory `/tmp/vmware-config3/vsock-only'
    Unable to make a vsock module that can be loaded in the running kernel:
    insmod: error inserting '/tmp/vmware-config3/vsock.o': -1 Unknown symbol in module

  6. #6
    Join Date
    Feb 2007
    Location
    New Zealand
    Beans
    826
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: VMware server 2 vsock warning

    I have vmware server 2 working on 2 Intrepid installations, a desktop and a server.

    When I upgraded these two machines to Intrepid I was using vmware server 1.06. I had the vsock error on one machine when re-compiling the drivers but not the other. I used the patch someone else mentioned to get that one working.

    In one install I had difficulty with the header files. I think the Intrepid upgrade failed to get the right ones. This would be worth checking - perhaps uninstall and re-install them?

    In both cases I had a warning about the version of gcc (I think) being used but the final product worked fine.

    I have also heard of people having success with vmware serve 2 and the patch (even though it's supposedly only for 1.xx):
    http://ubuntu-tutorials.com/2008/11/...627-7-generic/
    Veloce
    Ubuntu 9.04 64bit on Dell Vostro 1510, Core2 Duo T8100, Nvidia 8400M , Intel 1395 Wireless.
    OK: Wireless, kvm, Canon irc2880, Synergy.

  7. #7
    Join Date
    Nov 2008
    Beans
    2

    Re: VMware server 2 vsock warning

    Quote Originally Posted by remy06 View Post
    Code:
    WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
    WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
    This is because vsock depends on symbols from vmci module; the information is missing when vsock is built. I got vsock to build like this. (You need to have already installed vmware tools.)

    Code:
    $ cd /tmp
    $ tar xf /usr/lib/vmware-tools/modules/source/vmci.tar
    $ tar xf /usr/lib/vmware-tools/modules/source/vsock.tar
    $ cd vmci-only
    $ make
    $ cp Module.symvers ../vsock-only
    $ cd ../vsock-only
    $ make
    Copy /tmp/vsock.o to the appropriate location in /lib/modules, rerun 'depmod -a' etc.

    You also need to change
    Code:
    answer VSOCK_CONFED no
    to
    Code:
    answer VSOCK_CONFED yes
    in /etc/vmware-tools/locations so that /etc/init.d/vmware-tools will load vsock on startup.

  8. #8
    Join Date
    Jul 2006
    Location
    Nantes, France
    Beans
    39
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: VMware server 2 vsock warning

    ? But vmware-tools is build on guest machines, here the error occurs within host?

  9. #9
    Join Date
    Nov 2008
    Beans
    2

    Re: VMware server 2 vsock warning

    Oops, I misread the original message. I got a similar error trying to install vmware tools in a guest, and the above was how I solved that.

    It does look like the cause for the error in the host is the same though. Does vmci get compiled for the host also? Can you get the Module.symvers file from it?

  10. #10
    Join Date
    Nov 2007
    Beans
    11
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Re: VMware server 2 vsock warning

    Quote Originally Posted by dev13 View Post
    Oops, I misread the original message. I got a similar error trying to install vmware tools in a guest, and the above was how I solved that.

    It does look like the cause for the error in the host is the same though. Does vmci get compiled for the host also? Can you get the Module.symvers file from it?
    Yup, you can get it in the host/server version of vmware also.

    I've patched the vmware-config.pl script with attached patch and with that I solved this issue. Thanks for pointing me at the right direction how to solve this.

    This patch is for the most recent 2.0.0 version of VMWare: 122956
    Attached Files Attached Files
    Last edited by delgurth; November 28th, 2008 at 03:26 PM.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •