didier
Contributor
Contributor

6.5 segfault in F10-beta

Running Fedora 10 Beta (kernel 2.6.27-0.370.rc8 , glibc-2.8.90-12) :

  1. vmware-modconfig --console --install-all

results in :

/usr/lib/vmware/bin/launcher.sh: line 231: 11405 Segmentation fault "$binary" "$@"

dmesg reveals :

vmware-modconfi[11405]: segfault at 0 ip 000000321bc83b94 sp 00007fff532a2eb0 error 4 in libc-2.8.90.so[321bc00000+16c000]

Has anyone successfully patched 6.0.5 to run with 2.6.27 ?

Best regards,

Didier

Tags (4)
0 Kudos
24 Replies
mulicheng
Contributor
Contributor

Having the same issue. Can't build the kernel modules in fc10-beta.

0 Kudos
admin
Immortal
Immortal

We've had a developer hit this internally as well so hopefully we'll be able to track it down. In the meantime you can write a fairly simple shell script to install the kernel modules. Just untar all the modules in /usr/lib/vmware/modules/source, run make and then copy the module to /lib/modules/`uname -r`/misc, run depmod -a, and run /etc/init.d/vmware restart.

-jay

0 Kudos
didier
Contributor
Contributor

Thanks Jay, manually compiling the modules - as an interim solution - seems to work fine.

Some minor nuisances :

1.

$ make

cc1: error: unrecognized command line option "-m486"

make: *** http://ppuser-stub.o Error 1

2.

  1. service vmware start

Starting VMware services:

Virtual machine monitor

Virtual machine communication interface

Blocking file system

Virtual ethernet

dmesg :

/dev/vmmon[27599]: Module vmmon: registered with major=10 minor=165

/dev/vmmon[27599]: Initial HV check: anyNotCapable=0 anyUnlocked=0 anyEnabled=0 anyDisabled=1

/dev/vmmon[27599]: HV check: anyNotCapable=0 anyUnlocked=0 anyEnabled=0 anyDisabled=1

/dev/vmmon[27599]: Module vmmon: initialized

/dev/vmci[27612]: VMCI: Driver initialized.

/dev/vmci[27612]: Module vmci: registered with major=10 minor=59

/dev/vmci[27612]: Module vmci: initialized

SELinux: initialized (dev vmblock, type vmblock), uses genfs_contexts

/dev/vmnet: open called by PID 27673 (vmnet-bridge)

/dev/vmnet: hub 0 does not exist, allocating memory.

/dev/vmnet: port on hub 0 successfully opened

bridge-wlan0: is a Wireless Adapter

bridge-wlan0: up

bridge-wlan0: attached

/dev/vmnet: open called by PID 28222 (vmnet-dhcpd)

/dev/vmnet: hub 8 does not exist, allocating memory.

/dev/vmnet: port on hub 8 successfully opened

/dev/vmnet: open called by PID 28226 (vmnet-natd)

/dev/vmnet: port on hub 8 successfully opened

/dev/vmnet: open called by PID 28230 (vmnet-netifup)

/dev/vmnet: port on hub 8 successfully opened

vmnet8: no IPv6 routers present

(but networking works fine)

Regards and thanks again,

Didier

0 Kudos
zenocolo
Contributor
Contributor

Guys, you are to fast for me, I have same problem f10 beta/ vm 6.5:

Here what I did:

- untared archives

- run make in each dir

then:

# ls

vmblock.o vmci.o vmmon.o vmnet.o vmppuser-only vsock-only

vmblock-only vmci-only vmmon-only vmnet-only vmppuser.tar vsock.tar

vmblock.tar vmci.tar vmmon.tar vmnet.tar vsock.o

# cp *.o /lib/modules/`uname -r`/misc

# depmod -a

# /etc/init.d/vmware restart.

Usage: vmware {start|stop|status|restart|stoppable}

# /etc/init.d/vmware restart

Stopping VMware services:

Virtual machine communication interface

Virtual machine monitor

Blocking file system

Starting VMware services:

Virtual machine monitor

Virtual machine communication interface

Blocking file system

Virtual ethernet

# vmware

Logging to /tmp/vmware-root/setup-21851.log

modinfo: could not find module vmmon

modinfo: could not find module vmnet

modinfo: could not find module vmblock

modinfo: could not find module vmci

modinfo: could not find module vsock

modinfo: could not find module vmmon

modinfo: could not find module vmnet

modinfo: could not find module vmblock

modinfo: could not find module vmci

modinfo: could not find module vsock

/usr/lib/vmware/bin/launcher.sh: line 231: 21851 Segmentation fault "$binary" "$@"

Any advice?

tnx in advance

0 Kudos
admin
Immortal
Immortal

They probably need to be named *.ko instead of *.o.

0 Kudos
zenocolo
Contributor
Contributor

chef, many thanks, this solved it... i copyed the wrong files over Smiley Wink

0 Kudos
gjmoed
Contributor
Contributor

Guys, same problem here with rawhide, put a strace on it, it bombs out on enumerating binary modules dir, so I did:

mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

And voila, no more segfaults...

0 Kudos
mulicheng
Contributor
Contributor

I can build the modules manually (except vmppuser as noted before w/ -m486) and install them. The vmware service reports success on loading them all:

Starting VMware services:

Virtual machine monitor

[ OK ]

Virtual machine communication interface

[ OK ]

Blocking file system

[ OK ]

Virtual ethernet

[ OK ]

Shared Memory Available

[ OK ]

When I try to run vmware or vmplayer, I get:

vermagic: 2.6.27.4-58.fc10.x86_64 SMP mod_unload

filename: /lib/modules/2.6.27.4-58.fc10.x86_64/misc/vmmon.ko

license: GPL v2

description: VMware Virtual Machine Monitor.

author: VMware, Inc.

srcversion: 96CBF0250D0FB3F01BFBFFC

depends:

vermagic: 2.6.27.4-58.fc10.x86_64 SMP mod_unload

process 6566: Attempt to remove filter function 0x7f7245a36c40 user data 0x183e6a0, but no such filter has been added

I previously moved the binary modules directory but that didn't help.

I've tried this with 2.6.27.4-47.rc3 as well as 2.6.27.4-58

0 Kudos
mulicheng
Contributor
Contributor

After searching around a bit, I found that starting haldaemon fixes the filter problem.

/etc/init.d/haldaemon start

0 Kudos
Noel
Expert
Expert

We've had a developer hit this internally as well so hopefully we'll be able to track it down. In the meantime you can write a fairly simple shell script to install the kernel modules. Just untar all the modules in /usr/lib/vmware/modules/source, run make and then copy the module to /lib/modules/`uname -r`/misc, run depmod -a, and run /etc/init.d/vmware restart.

While VMware works on putting out a fixed version of Workstation, attached is the script I use for Fedora 10 whenever a new kernel is released. WARNING: you're on your own. No warranty or support, even if you erase your entire hard drive.

0 Kudos
jimlucas
Contributor
Contributor

Noel,

Thank you for the script. That appears to have done the trick.

0 Kudos
NLSurfMan
Contributor
Contributor

I have tried to run the script vmware-build-modules, but this is the output. Not surprisingly, VMWare Workstation still doesn't start, but bombs out withthe following message:

Nov 28 10:40:29 localhost kernel: vmware-modconfi[10637]: segfault at 0 ip 0000003fa7681d64 sp 00007fff7d81af00 error 4 in libc-2.9.so[3fa7600000168000]+

Obviously, I am not a Linux guru (yet Smiley Wink, but still I would like to get VMWare to work on my Fedora 10 box. Attached is the output of that script.

Versin info: Linux PCWJ 2.6.27.5-117.fc10.x86_64 #1 SMP Tue Nov 18 11:58:53 EST 2008 x86_64 x86_64 x86_64 GNU/Linux

0 Kudos
smpouh
Contributor
Contributor

Noel,

Many thanks for the script. It works wonderfully.

Cheers,

smpouh

0 Kudos
NLSurfMan
Contributor
Contributor

I solved my issue... Turns out I didn't have kernel-devel installed.

And the script works beautiful!

0 Kudos
davidbailey
Contributor
Contributor

Just a heads up. I experienced this same problem in openSUSE 11.1 RC2 kernel Linux 2.6.27.7-8-default #1 SMP 2008-11-25 00:02:37 +0100 x86_64 x86_64 x86_64 GNU/Linux.

Thanks for the solution.

0 Kudos
dledwith
Contributor
Contributor

I'm having a problem installing workstation in openSUSE 11.1 kernel 2.6.27.7-9-default. I am running the 64 bit version of suse. I'm a linux beginner so I'm not sure if I applied the fix properly or not. I downloaded the vmware-build-modules script to my desktop and viewed it in gedit but I don't know how to run it. Thank you in advance for any help I can get on this forum. Below is what I see when I run vmware & command after installing the .rpm.

I also uninstalled the .rpm and installed with the .bundle but got the same result. I went back and made sure I had the following software installed also per a forum post.

gcc

gcc++

make

binutils

kernel-source

Danny@linux-fpx7:~> vmware &

11983

Danny@linux-fpx7:~> Logging to /tmp/vmware-Danny/setup-11988.log

modinfo: could not find module vmmon

modinfo: could not find module vmnet

modinfo: could not find module vmblock

modinfo: could not find module vmci

modinfo: could not find module vsock

modinfo: could not find module vmmon

modinfo: could not find module vmnet

modinfo: could not find module vmblock

modinfo: could not find module vmci

modinfo: could not find module vsock

0 Kudos
CharlieM
Enthusiast
Enthusiast

I'm having a problem installing workstation in openSUSE 11.1 kernel 2.6.27.7-9-default. I am running the 64 bit version of suse. I'm a linux beginner so I'm not sure if I applied the fix properly or not. I downloaded the vmware-build-modules script to my desktop and viewed it in gedit but I don't know how to run it. Thank you in advance for any help I can get on this forum. Below is what I see when I run vmware & command after installing the .rpm.

I also uninstalled the .rpm and installed with the .bundle but got the same result. I went back and made sure I had the following software installed also per a forum post.

Danny@linux-fpx7:~> vmware &

11983

Danny@linux-fpx7:~> Logging to /tmp/vmware-Danny/setup-11988.log

modinfo: could not find module vmmon

modinfo: could not find module vmnet

modinfo: could not find module vmblock

modinfo: could not find module vmci

modinfo: could not find module vsock

modinfo: could not find module vmmon

modinfo: could not find module vmnet

modinfo: could not find module vmblock

modinfo: could not find module vmci

modinfo: could not find module vsock

I didn't have to run the script you mentioned (Fedora 10 x86_64), but I did have to use the workaround posted earlier in this thread:

mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

If you do want to run that script you downloaded, you must first make it executable by typing "chmod +x vmware-build-modules" and then execute it by typing "./vmware-build-modules". But I would try the renaming first, as it's less complicated and (if it works) will let you use the new automatic module building system in vmware.

To do either of these, you will have to have root privs.

0 Kudos
dledwith
Contributor
Contributor

Thank you so much Charlie. I can't believe the fix was SOO easy. I just needed someone like you to confirm what I needed to do. Happy New Year to you and everyone one else reading this thread.

Danny

0 Kudos
lreed22
Contributor
Contributor

Thank you for the fix Noel, it worked great for openSuse 11.1, WS 6.5.1

0 Kudos