VMware server 2 vsock warning

[chaeron]

Rumor has it the next version of VMWare Server will fix this

When???

[CyberAngel]

Same problem here of course

[TpyKv]

yeah same problem here too, every time I upgrade, I have similar issues...

DOH!

[dev13]

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.)

$ 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

answer VSOCK_CONFED no

to

answer VSOCK_CONFED yes

in /etc/vmware-tools/locations so that /etc/init.d/vmware-tools will load vsock on startup.

[thierrybo]

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

[dev13]

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?

[delgurth]

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

[micahel]

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

very good! tested the patch right now and it works OK!

kubuntu 8.10 intrepid

uname -a
Linux host 2.6.27-10-generic #1 SMP Fri Nov 21 19:19:18 UTC 2008 x86_64 GNU/Linux

lsmod |grep v
vmnet                  54732  3
vsock                  31536  0
vmci                   65832  1 vsock
vmmon                  85968  0
(...)

thanks for the good job!

cheers, michael

[chaeron]

Just upgraded my VMWare Workstation install to the "hot-off-the-press" 6.5.1 build-126130.

No joy in mudville, I'm afraid. The same problem exists. When you try to rebuild the vmware-toolbox, the vsock module will not insert in the Intrepid kernel.

Very disappointing....I was hoping that VMWare would have fixed this issue in the latest release.

So still no cut/paste between the host OS and the guest for now with Workstation 6.5.1.

Maybe next version....<sigh>

In the meantime, if some kind soul was able to create a similar patch for the Workstation /usr/bin/vmware-config-tools.pl script, that would be very much appreciated!

[bond00]

Nice work Delgurth! Worked perfectly for me as well. For those who don't know how to patch the vmware-config.pl file it's simply:

sudo patch /usr/bin/vmware-config.pl /path/to/vmware-config.pl.patch