Dominique,
The vsock module warning messages have always been there (its
been on our list of things to cleanup for awhile). They appear because
the vsock build has no knowledge of the vmci module build even though
vsock depends on vmci symbols. I believe that the kernel module loader
changed sometime before 2.6.27 to prevent modules with unknown symbols
from loading if the kernel was built with CONFIG_MODVERSIONS. This is
something I was going to look into internally but haven't had a chance
to test out yet.
The reporters have seen the following from dmesg:
home/user/vmxnet3h/hosted08/bora# insmod build/obj-x64/ws/modules/
local/2.6.27-4-generic/vsock/vsock.ko
insmod: error inserting 'build/obj-x64/ws/modules/local/2.6.27-4-
generic/vsock/vsock.ko': -1 Unknown symbol in module
A quick test to see if this is the problem would be to:
1. Build the vmci module
2. Copy Module.symvers from vmci => vsock
3. Build vsock
4. Try loading the module.
All of that being said, ws shouldn't be segfaulting on startup (it
should be able to load and run fine without the vsock module ... you
just will not be able to use vmci sockets).
A couple of questions:
1. Which process specifically is dying? vmware / vmware-vmx something
else?
2. Can you get us a core dump from the segfault?
3. Can you upload the relevant logs. On my machine they live in /tmp/
vmware-${USER} and <VM Directory>/vmware.log
4. Any other relevant debugging information you can think of.
Aaron
On Oct 21, 2008, at 6:34 AM, Dominique Leuenberger wrote:
> Hi,
>
> I know this is not the right list, but the problem might come up later
> in the open-vm-tools as well.
>
> I'm trying to make a VMware Workstation 6.5 start on a 2.6.27 kernel.
>
> Starting vmware itself gives a segfault, as the modules are not there
> and apparently compiling them seems more difficult than expected.
>
> So I went to /usr/lib/vmware/modules/sources nd untared all the
> archives.
>
> changing to every directory and executing make compiles them (except
> one.. for parallel port if I'm not mistaken, which sounds rather
> unimportant) and vsock.ko
>
> vsock fails with the following warnings:
> WARNING:
> "VMCIDatagram_CreateHnd" [/usr/lib/vmware/modules/source/vsock-only/
> vsock.ko] undefined!
> WARNING:
> "VMCIDatagram_DestroyHnd" [/usr/lib/vmware/modules/source/vsock-only/
> vsock.ko] undefined!
> WARNING:
> "VMCI_GetContextID" [/usr/lib/vmware/modules/source/vsock-only/
> vsock.ko]
> undefined!
> WARNING:
> "VMCIDatagram_Send" [/usr/lib/vmware/modules/source/vsock-only/
> vsock.ko]
> undefined!
>
> Needless to say, that modprobing this module does not work; all the
> others work.
>
> What would be the correct way to tackle this?
>
> Dominique
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> open-vm-tools-devel mailing list
> open-vm-tools-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
open-vm-tools-devel mailing list
open-vm-tools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
