VMware Communities
Tanker_Bob
Contributor
Contributor

VMWare Workstation 6.5 vsock module fails to install in Ubuntu 8.10RC1 guest

Workstaion 6.5 build 118116 installed in Kubuntu Linux 8.04.1 32-bit host, 2.6.24-21 kernel, 2GB RAM, NVidia 8800GTS video card. No problems installing there. Then I tried to install VMWare Tools in an Unbuntu 8.10RC1, kernel 2.6.27-7 guest with 512MB RAM assigned that was working fine under Workstation 6.05. Under 6.5, the vsock module failed to compile, giving the following error messages:

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 /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" undefined!

WARNING: "VMCIDatagram_DestroyHnd" undefined!

WARNING: "VMCIEvent_Subscribe" undefined!

WARNING: "VMCI_DeviceGet" undefined!

WARNING: "VMCIMemcpyFromQueueV" undefined!

WARNING: "VMCIQueuePair_Detach" undefined!

WARNING: "VMCI_GetContextID" undefined!

WARNING: "VMCIDatagram_Send" undefined!

WARNING: "VMCIQueuePair_Alloc" undefined!

WARNING: "VMCIEvent_Unsubscribe" undefined!

WARNING: "VMCIMemcpyToQueueV" 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-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.

I tried the open source vsock module dated 10/13/2008, but it didn't work either. I tried a fix suggested under the VMWare Server2.0 forum that involved editing the vsock headers and recompiling vsock, but it didn't work. Any help would be appreciated. It looks like all my Ubuntu 8.10RC1Intrepid Ibex VMs are now broken under Workstation 6.5. I need any help that anyone can provide. A substitute vsock would be great. Thanks.

Reply
0 Kudos
12 Replies
brianld
Contributor
Contributor

I'm having the same problem on the official Ubuntu 8.10 release (not RC).

Reply
0 Kudos
Tanker_Bob
Contributor
Contributor

Brian,

I did some more experimenation tonight. I deleted the original Ubuntu 8.10 guest and recreated the Intrepid release (not the RC) from scratch under Workstation 6.5. I enabled the accelerated 3D graphics and paravirtualization. Ubuntu 8.10 installed clean in the VM with no problems. After updating the initial install, I installed VMWare Tools. Same problem with both vsock and the X.org error. No 3D effects and the mouse doesn't transition out of the VM to the host without hitting ctrl-alt. No cut-and-paste between host and guest, either. It seems that VMWare Tools for 6.5 is broken for Intrepid guests. Intrepid guests worked fine in 6.0.5. The 6.5 update appears to be a regression for Linux guests. I guess we just wait for VMWare to get around to fixing it. Not a good use of my time or money.

I see others are noticing the issue as well. Maybe if more people highlight the issue, VMWare will take it seriously.

Reply
0 Kudos
Tanker_Bob
Contributor
Contributor

I wrote about this issue twice on my blog, and have had a large number of readers of the articles. The phrase "vmware tools ubuntu 8.10" or some combination of that is the top search criteria reaching the blog over the weekend. This is clearly an issue for a good number of folks. Does VMWare have any response at all? Do they acknowledge the problem than many of us are experiencing both with vsock and the X.org issue? Has anyone in the community come up with a workaround?

Since first finding this issue, I deleted the affected VM and installed Ubuntu 8.10 release version from scratch in a new VM fully configured as a 6.5 machine. The vsock and X.org 7.4.2 issues remain the same for VMWare Tools 6.5.0 build 118116.

It's hard to believe that VMWare didn't see this coming.

Reply
0 Kudos
borice
Contributor
Contributor

Still no solution? Has VMware turned the deaf ear towards us?

Reply
0 Kudos
alfredo4570
Contributor
Contributor

Hi,

in vsock, util.c won't compile because of an error with Log(buf); on lne 157.

This would work OK if the line were changed to

Log("%s\n", buf);

Unfortunately, you can't just edit util.c, because the next build moves from /tmp/vmware-config0/ to /tmp/vmware-config1/

Reply
0 Kudos
alfredo4570
Contributor
Contributor

Hi,

Even assuming that you can get util.c to compile, see my previous post, vsock.ko is undefined, see attachment.

Reply
0 Kudos
admin
Immortal
Immortal

Hello everyone,

Are you running Ubuntu x86 or x86-64 guests? I'll file a bug internally. I'm not sure why there's been no response on this.

Reply
0 Kudos
admin
Immortal
Immortal

One more thing, for those with the "ctrl-alt required to ungrab" issue, can you attach your guest's Xorg log to a post?

Thanks.

Reply
0 Kudos
baturcotte
Contributor
Contributor

I am seeing the same vsock module failure on OpenSUSE 11.1 RC1, 64 bit, kernel 2.6.26.7-4 on a 6.5.1 Windows host.

Reply
0 Kudos
Kaell
Contributor
Contributor

I have this issue as well.

To answer the question posed: I am running x86 guest.

Host: WinXP SP2 (32-bit on 32-bit CPU)

VMware: Server 2.0

Guest: Ubuntu 8.10 Desktop (32-bit) (kernel 2.6.27-9-generic)

Reply
0 Kudos
tconant
Contributor
Contributor

Is there any resolution to this issue? I'm having the same problem on debian 'Lenny'. vsock fails on an undefined symbol. Resulting in vmware not grabbing/ungrabbing my mouse when I enter/exit the window of the guest OS. Changing my kernels from 2.6.26.1 to 2.6.24.7.did not fix the problem (however it fails slightly different now). With the 2.6.26.1 kernel it would fail lacking on one symbol. With 2.6.24.7 i get the exact error reported in the first message of this post.

Bellow is output from vmware tools. Another intreseting thing (i.e. bug) is that even though I running 2.6.24.7 it recreates the wrong initrd file. After building vmxnet module it build initd for 2.6.26 instead of 2.6.24.

update-initramfs: Generating /boot/initrd.img-2.6.26-1-686

The installation of VMware Tools 7.8.4 build-126130 for Linux completed

successfully. You can decide to remove this software from your system at any

time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

Before running VMware Tools for the first time, you need to configure it by

invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want

this program to invoke the command for you now? yes

Stopping VMware Tools services in the virtual machine:

Guest operating system daemon: done

Virtual Printing daemon: done

VMware User Agent (vmware-user): done

Blocking file system: done

Unmounting HGFS shares: done

Guest filesystem driver: done

Guest memory manager: done

VM communication interface: done

None of the pre-built vmmemctl modules for VMware Tools is suitable for your

running kernel. Do you want this program to try to build the vmmemctl module

for your system (you need to have a C compiler installed on your system)?

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running

kernel?

Extracting the sources of the vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.24.7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.24.7'

CC /tmp/vmware-config0/vmmemctl-only/backdoorGcc32.o

CC /tmp/vmware-config0/vmmemctl-only/os.o

CC /tmp/vmware-config0/vmmemctl-only/vmballoon.o

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

Building modules, stage 2.

MODPOST 1 modules

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

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

make[1]: Leaving directory `/usr/src/linux-2.6.24.7'

cp -f vmmemctl.ko ./../vmmemctl.o

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

The vmmemctl module loads perfectly into the running kernel.

None of the pre-built vmhgfs modules for VMware Tools is suitable for your

running kernel. Do you want this program to try to build the vmhgfs module for

your system (you need to have a C compiler installed on your system)?

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.24.7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.24.7'

CC /tmp/vmware-config0/vmhgfs-only/backdoor.o

CC /tmp/vmware-config0/vmhgfs-only/backdoorGcc32.o

CC /tmp/vmware-config0/vmhgfs-only/bdhandler.o

CC /tmp/vmware-config0/vmhgfs-only/cpName.o

CC /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o

CC /tmp/vmware-config0/vmhgfs-only/cpNameLite.o

CC /tmp/vmware-config0/vmhgfs-only/dentry.o

CC /tmp/vmware-config0/vmhgfs-only/dir.o

CC /tmp/vmware-config0/vmhgfs-only/file.o

CC /tmp/vmware-config0/vmhgfs-only/filesystem.o

CC /tmp/vmware-config0/vmhgfs-only/fsutil.o

CC /tmp/vmware-config0/vmhgfs-only/hgfsBd.o

CC /tmp/vmware-config0/vmhgfs-only/hgfsEscapeLinux.o

CC /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o

CC /tmp/vmware-config0/vmhgfs-only/inode.o

CC /tmp/vmware-config0/vmhgfs-only/kernelStubsLinux.o

CC /tmp/vmware-config0/vmhgfs-only/link.o

CC /tmp/vmware-config0/vmhgfs-only/messageBackdoor.o

CC /tmp/vmware-config0/vmhgfs-only/message.o

CC /tmp/vmware-config0/vmhgfs-only/module.o

CC /tmp/vmware-config0/vmhgfs-only/page.o

CC /tmp/vmware-config0/vmhgfs-only/request.o

CC /tmp/vmware-config0/vmhgfs-only/rpcout.o

CC /tmp/vmware-config0/vmhgfs-only/staticEscape.o

CC /tmp/vmware-config0/vmhgfs-only/stubs.o

CC /tmp/vmware-config0/vmhgfs-only/super.o

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

Building modules, stage 2.

MODPOST 1 modules

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

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

make[1]: Leaving directory `/usr/src/linux-2.6.24.7'

cp -f vmhgfs.ko ./../vmhgfs.o

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

The vmhgfs module loads perfectly into the running kernel.

None of the pre-built vmxnet modules for VMware Tools is suitable for your

running kernel. Do you want this program to try to build the vmxnet module for

your system (you need to have a C compiler installed on your system)?

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.24.7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.24.7'

CC /tmp/vmware-config0/vmxnet-only/vmxnet.o

Building modules, stage 2.

MODPOST 1 modules

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

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

make[1]: Leaving directory `/usr/src/linux-2.6.24.7'

cp -f vmxnet.ko ./../vmxnet.o

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

The vmxnet module loads perfectly into the running kernel.

update-initramfs: Generating /boot/initrd.img-2.6.26-1-686

None of the pre-built vmblock modules for VMware Tools is suitable for your

running kernel. Do you want this program to try to build the vmblock module

for your system (you need to have a C compiler installed on your system)?

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.24.7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.24.7'

CC /tmp/vmware-config0/vmblock-only/linux/block.o

CC /tmp/vmware-config0/vmblock-only/linux/control.o

CC /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o

CC /tmp/vmware-config0/vmblock-only/linux/dentry.o

CC /tmp/vmware-config0/vmblock-only/linux/file.o

CC /tmp/vmware-config0/vmblock-only/linux/filesystem.o

CC /tmp/vmware-config0/vmblock-only/linux/inode.o

CC /tmp/vmware-config0/vmblock-only/linux/module.o

CC /tmp/vmware-config0/vmblock-only/linux/stubs.o

CC /tmp/vmware-config0/vmblock-only/linux/super.o

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

Building modules, stage 2.

MODPOST 1 modules

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

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

make[1]: Leaving directory `/usr/src/linux-2.6.24.7'

cp -f vmblock.ko ./../vmblock.o

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

The vmblock module loads perfectly into the running kernel.

The VMware FileSystem Sync Driver (vmsync) is a new feature that

creates backups of virtual machines. Please refer to the VMware Knowledge Base

for more details on this capability. Do you wish to enable this feature?

None of the pre-built vmci modules for VMware Tools is suitable for your

running kernel. Do you want this program to try to build the vmci module for

your system (you need to have a C compiler installed on your system)?

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.24.7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.24.7'

CC /tmp/vmware-config0/vmci-only/kernelStubsLinux.o

CC /tmp/vmware-config0/vmci-only/vmciDatagram.o

CC /tmp/vmware-config0/vmci-only/vmci_drv.o

CC /tmp/vmware-config0/vmci-only/vmciEvent.o

CC /tmp/vmware-config0/vmci-only/vmciGuestDs.o

CC /tmp/vmware-config0/vmci-only/vmciGuestKernelIf.o

CC /tmp/vmware-config0/vmci-only/vmciKernelIf.o

CC /tmp/vmware-config0/vmci-only/vmciProcess.o

CC /tmp/vmware-config0/vmci-only/vmciQueuePair.o

CC /tmp/vmware-config0/vmci-only/vmciUtil.o

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

Building modules, stage 2.

MODPOST 1 modules

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

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

make[1]: Leaving directory `/usr/src/linux-2.6.24.7'

cp -f vmci.ko ./../vmci.o

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

The vmci module loads perfectly into the running kernel.

None of the pre-built vsock modules for VMware Tools 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.24.7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.24.7'

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

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" undefined!

WARNING: "VMCIDatagram_DestroyHnd" undefined!

WARNING: "VMCIEvent_Subscribe" undefined!

WARNING: "VMCI_DeviceGet" undefined!

WARNING: "VMCIMemcpyFromQueueV" undefined!

WARNING: "VMCIQueuePair_Detach" undefined!

WARNING: "VMCI_GetContextID" undefined!

WARNING: "VMCIDatagram_Send" undefined!

WARNING: "VMCIQueuePair_Alloc" undefined!

WARNING: "VMCIEvent_Unsubscribe" undefined!

WARNING: "VMCIMemcpyToQueueV" 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-2.6.24.7'

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

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

The vsock module loads perfectly into the running kernel.

Detected X.org version 7.3.2.

Reply
0 Kudos
pdwalker
Contributor
Contributor

ubuntu 8.10 under vmware 6.5 for windows xp.

It's working for me now after following these instructions:

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

Reply
0 Kudos