VMware Communities: Message List - vsock module won't insmod on Ubuntu 8.10 (intrepid)

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

rahvee — Fri, 14 Aug 2009 22:25:27 GMT

You have to use ubuntu server, not ubuntu desktop. See here:

http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software
(I found this by going to vmware.com. Click on Resources -->
Compatibility guides. and finally "View the Guest/Host OS tab on the
VMWare Compatibility Guide")

Search for: VMWare Server, 2.0.1, Partner Canonical, Host OS, Linux:
Results: Ubuntu Server (not desktop)

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

rahvee — Fri, 14 Aug 2009 22:23:22 GMT

You have to use ubuntu server, not ubuntu desktop. See here:

Search for: VMWare Server, 2.0.1, Partner Canonical, Host OS, Linux:
Results: Ubuntu Server (not desktop)

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

thierrybo — Mon, 08 Dec 2008 20:58:39 GMT

This issue has been solved, see http://ubuntuforums.org/showthread.php?t=975084&page=2 , there is sa patch for build 122956

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

jmsvmware — Fri, 28 Nov 2008 08:36:22 GMT

Yes starfear, your fix did the trick in Ibex 32bit. I didn't notice any difference in funtionality before and after this fix though, everything seems to be just fine as it did before also.

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

starfear — Wed, 26 Nov 2008 13:42:53 GMT

Resolve for 2.6.27.7 vmware-server2 :

remove from /tmp all /tmp/vmware-config* if exist.

rm -rf /tmp/vmware-config*

In vmware-config.pl, in "sub build_module" :

##### string 4123 ############# INSERT

if ($name eq 'vsock') {
system('ln -sf /tmp/vmware-config1/vmci-only/Module.symvers /tmp/vmware-config2/vsock-only');
print wrap ('My code');
}

######### BEFORE

print wrap('Building the ' . $name . ' module.' . "\n\n", 0);
if (system(shell_string($gHelper{'make'}) . ' -C '
. shell_string($build_dir . '/' . $name . '-only')
. ' auto-build ' . (($gSystem{'smp'} eq 'yes') ? 'SUPPORT_SMP=1 '
: '')
. (($gOption{'kernel_version'} ne '')?
shell_string('VM_UNAME=' . $gOption{'kernel_version'}) . ' ':'')
. shell_string('HEADER_DIR=' . db_get_answer('HEADER_DIR')) . ' '
. shell_string('CC=' . $gHelper{'gcc'}) . ' '
. shell_string('GREP=' . $gHelper{'grep'}) . ' '
. shell_string('IS_GCC_3='
. (($gSystem{'gcc_version'} =~ /^3\./) ? 'yes' : 'no')))) {
print wrap('Unable to build the ' . $name . ' module.' . "\n\n", 0);
return 'no';
}

if ($gOption{'kernel_version'} eq '')
{

## Don't use the force flag: the module is supposed to perfectly load

if (try_module($name, $build_dir . '/' . $name . '.o', 0, 1)) {
print wrap('The ' . $name . ' module loads perfectly into the running kernel.'
. "\n\n", 0);

######## COMMENT NEXT LINE
######## remove_tmp_dir($build_dir);
######## END

After vmware-config.pl you can:
rm -rf /tmp/vmware-config*

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

Igor Toledo — Sat, 22 Nov 2008 01:06:40 GMT

Done the problem!

install Linux-PAM and the auth via web will work

http://www.slackbr.org/forum/viewtopic.php?f=3&t=17389&sid=4d36354faa4770f3cbe5883478d7f896

for Slackware 12.1 x86: http://www.linuxpackages.net/search_view.php?by=name&name=pam&ver=12.1

for Slamd64 12.1 x64: http://darkstar.ist.utl.pt/slackware/addon/linuxpackages/Slackware-12.0-x86_64/Library/Linux-PAM/

\o/

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

calibre97 — Sun, 09 Nov 2008 05:20:43 GMT

I got the same problem on Ibex 32 bit with an XP guest previously created in VMWare Server 1.06 under Heron. I got VMWare Server to run and I logged in with FireFox and I added the guest vmdk to the data store in the browser but I couldn't get it to power up and I reran the config.pl and same no joy with VSOCK.

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

millwaelder — Thu, 06 Nov 2008 19:21:34 GMT

Ubuntu 8.10 - 64bit - (2.6.27-7-server), VMware 2.0 (122956)

Only one command line has been added to /etc/vmware/config

xkeymap.nokeycodeMap = TRUE

Fixed all keyboard problems at once.

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

Igor Toledo — Thu, 06 Nov 2008 03:50:17 GMT

Put this in ~/.vmware/config:

xkeymap.keycode.108 = 0x138 # Alt_R
xkeymap.keycode.106 = 0x135 # KP_Divide
xkeymap.keycode.104 = 0x11c # KP_Enter
xkeymap.keycode.111 = 0x148 # Up
xkeymap.keycode.116 = 0x150 # Down
xkeymap.keycode.113 = 0x14b # Left
xkeymap.keycode.114 = 0x14d # Right
xkeymap.keycode.105 = 0x11d # Control_R
xkeymap.keycode.118 = 0x152 # Insert
xkeymap.keycode.119 = 0x153 # Delete
xkeymap.keycode.110 = 0x147 # Home
xkeymap.keycode.115 = 0x14f # End
xkeymap.keycode.112 = 0x149 # Prior
xkeymap.keycode.117 = 0x151 # Next
xkeymap.keycode.78 = 0x46 # Scroll_Lock
xkeymap.keycode.127 = 0x100 # Pause
xkeymap.keycode.133 = 0x15b # Meta_L
xkeymap.keycode.134 = 0x15c # Meta_R
xkeymap.keycode.135 = 0x15d # Menu

from here

Still Im waiting a solution for logon VMWARE SERVER 2 on Linux kernel 2.6.26.2 ...

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

yquirion — Wed, 05 Nov 2008 15:19:38 GMT

Dear all:

I'm experiencing the same problem. Also, since I upgrade Ubunto 32bity from 8.04 to 8.10, I'm having lot of problem with my vm (Windows XP PRO. Some keys on the keyboard doesn't seems working, like CTRL-ALT-INS (to logon into windows XP).

If somebody has some hints, please let me know.

Regards,

Yanick

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

CheckSix — Wed, 05 Nov 2008 15:06:58 GMT

I got exactly the same behavior.

Ubuntu 8.10 | Linux 2.6.27-7-server #1 SMP x86_64 GNU/Linux

VMware-server-2.0.0-122956.x86_64

I tried this two links without success too.

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

http://www.huschi.net/33_310_de.html

Someone already got it running?

-Markus

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

borice — Mon, 03 Nov 2008 06:02:53 GMT

bump - any solution yet?

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

Igor Toledo — Fri, 17 Oct 2008 03:02:03 GMT

and did you log on at http://localhost:8222 or 8333 ? Here just wrong user/pwd returns.

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

stevemaring — Thu, 16 Oct 2008 12:47:16 GMT

actually, the instructions at http://kramfs.com/2008/07/13/vmware-server-2-unable-to-build-the-vsock-module/ seemed to work for me from a compilation standpoint. However, I STILL don't see vsock in my lsmod list

when I try to depmod it I just get "WARNING: Can't read module vsock: No such file or directory"

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

Igor Toledo — Thu, 16 Oct 2008 04:44:03 GMT

same problem on Slamd64 12.1,

VMware-server-2.0.0-116503.x86_64 fails to autenticate (no root or whatever login accepts)

vmware-config.pl:

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: Entrando no diretório `/tmp/vmware-config18/vsock-only'
make -C /lib/modules/2.6.26.2/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entrando no diretório `/home/me/kernel/2.6.26.2'
make -C /usr/src/linux-2.6.26.2 O=/home/me/kernel/2.6.26.2/. modules
CC [M] /tmp/vmware-config18/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config18/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config18/vsock-only/linux/util.o
CC [M] /tmp/vmware-config18/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config18/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config18/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config18/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config18/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config18/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config18/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config18/vsock-only/vsock.ko
make[1]: Saindo do diretório `/home/me/kernel/2.6.26.2'
cp -f vsock.ko ./../vsock.o
make: Saindo do diretório `/tmp/vmware-config18/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config18/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.
http:// Press the Enter key to continue.

I tried these workarounds but no success:

nothing !

What to do? rollback to 2.4x kernel?

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

alphadog4 — Thu, 16 Oct 2008 03:28:03 GMT

Interesting. So, what happens when Ubuntu and other distros come out of beta with kernel version 2.6.27? When I upgrade my systems running VMWare Server 2, will it all come down around my head?

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

Illaire — Thu, 16 Oct 2008 00:24:36 GMT

jaood wrote:
Hi - did you manage to solve this issue? I'm having the same problem with debian lenny.

You can't. VMware 2 is not compatible with 2.6.27 and later kernels. Perhaps next version will be?

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

piripallo — Wed, 15 Oct 2008 21:17:36 GMT

I have the same problem using Debian sid and Ubuntu intrepid (32 bit).

Only with 2.6.27.xx kernels.

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

jaood — Tue, 14 Oct 2008 22:54:18 GMT

Hi - did you manage to solve this issue? I'm having the same problem with debian lenny.

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

stevemaring — Thu, 02 Oct 2008 15:12:03 GMT

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 [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-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