VMware Communities: Message List - vsock fails to build during install of VMware Server 2.0.1 on Ubuntu 9.04

Re: vsock fails to build during install of VMware Server 2.0.1 on Ubuntu 9.04

ejb11235 — Thu, 09 Jul 2009 17:55:42 GMT

kramfs -- I've used your approach but I found that if I reran vmware-config.pl later on, it complained that there were modules present that it hadn't installed, and then I would have to go back and manually remove the modules before I could run vmware-config.pl. ryoohki's approach seems to avoid that by fixing the source first and then letting vmware-config.pl do the compilation.

Unfortunately, my joy at getting the bridged mode to work was short-lived. Once I rebooted, bridged mode no longer worked, even though ismod showed that vsock was loaded. So apparently my conclusions were incorrect. Fortunately I don't really need bridged mode at this time, so I'm not going to worry about it. I'm not terribly impressed with Server 2 ... the web interface is unstable and slow.

--eric

Re: vsock fails to build during install of VMware Server 2.0.1 on Ubuntu 9.04

kramfs — Thu, 09 Jul 2009 15:10:01 GMT

I had exactly the same problem but I eventually managed to fixed it.

I documented the process here:

http://kramfs.com/vmware-server-2-unable-to-build-the-vsock-module/

Re: vsock fails to build during install of VMware Server 2.0.1 on Ubuntu 9.04

kramfs — Thu, 09 Jul 2009 15:02:28 GMT

I had exactly the same problem!

I was able to fixed it using the solution posted on this article which worked perfectly:

http://kramfs.com/vmware-server-2-unable-to-build-the-vsock-module/

Re: vsock fails to build during install of VMware Server 2.0.1 on Ubuntu 9.04

ejb11235 — Sun, 05 Jul 2009 23:00:46 GMT

There's also a patch that modifies vmware-config.pl at http://ubuntuforums.org/showthread.php?t=975084&page=2 I used your instructions above, so I don't know if the patch works. Either way, this solved the problem I was having with bridged mode not working. There's another "fix" out there that involves recompiling vsock after vmware-config.pl runs, but if you do that then bridged mode doesn't work. The key to figuring out was doing an lsmod.

lsmod |grep v
vmnet 54732 3**
vsock 31536 0
vmci 65832 1 vsock
vmmon 85968 0

Vsock wasn't showing up until I did what you are suggesting ... now bridged mode works, and the virtual machines are showing up on my DHCP server.

Re: vsock fails to build during install of VMware Server 2.0.1 on Ubuntu 9.04

ryoohki — Mon, 22 Jun 2009 13:27:14 GMT

# Here's a simple batch file for fixing this error

cd /usr/lib/vmware/modules/source || exit

tar xvf vmci.tar

if [ ! -f vsock.tar.original \] ; then

mv vsock.tar vsock.tar.original && cp vsock.tar.original vsock.tar

else

/bin/cp vsock.tar.original vsock.tar

fi

tar xvf vsock.tar

cd vmci-only

make || exit

mv Module.symvers ../vsock-only

cd ..

mv -i vsock.tar vsock.tar.bak_$( date '+%F_%H-%M-%S' ) && tar cvf vsock.tar vsock-only

echo "===== List of backups of vsock.tar in /usr/lib/vmware/modules/source ====="

ls -1trd vsock.tar.bak_*

echo

rm -rf vsock-only vmci-only

#now run:

#/usr/bin/vmware-config.pl

Re: vsock fails to build during install of VMware Server 2.0.1 on Ubuntu 9.04

jamarju — Sat, 16 May 2009 18:11:54 GMT

This worked for me: http://www.mail-archive.com/open-vm-tools-devel@lists.sourceforge.net/msg00123.html

You basically have to untar vmci.tar (in /usr/lib/vmware/modules/source), then build the module with 'make'. Then untar vsock.tar and copy the "Modules.symvers" file resulting from the previous compilation into the "vsock-only" directory. Rebuild the vsock.tar file and run "vmware-config.pl". Now it should compile just fine.

Javier

vsock fails to build during install of VMware Server 2.0.1 on Ubuntu 9.04

llamahunter — Mon, 04 May 2009 22:54:56 GMT

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