Dominique,
Apologies for the delay in my response ... I was on vacation last
week.
Unfortunately my change did not make it into the workstation 6.5.1
release but
is in the latest open-vm-tools release (11-18)
The changes are only makefile related. In particular the changes are in:
open-vm-tools-2008.11.18-130226/modules/linux/vsock/Makefile.kernel
open-vm-tools-2008.11.18-130226/modules/linux/vsock/Makefile
open-vm-tools-2008.11.18-130226/modules/linux/vmci/Makefile.kernel
open-vm-tools-2008.11.18-130226/modules/linux/vmci/Makefile
Hopefully the change will make it into the next patch release for WS.
Let me know if there are more issues,
Aaron
On Nov 26, 2008, at 7:06 AM, Dominique Leuenberger wrote:
>>>> On 10/21/2008 at 6:51 PM, Aaron Rolett <[EMAIL PROTECTED]> wrote:
>> 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,
>
> In reference to the mail from Oct 21 on the open-vm-tools mailing
> list,
> I wanted to ask if you know about anything that is going to change in
> the next days / weeks / months?
>
> As openSUSE 11.1 is due to be released, I hear more and more requests
> from users with failing module compilations, due to this error (last
> one
> was at https://bugzilla.novell.com/show_bug.cgi?id=447430 )
>
> I hoped at least that the new VM WS 6.5.1 would solve something in
> this
> respect, but it did not :(
>
> Thanks for your thoughts,
> 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
