vmware-server not working after kernel update

[Feirefis]

Re: vmware-server not working after kernel update

I found the fix for my problem at Zybez Runescape. Hope it is OK to copy the advice from "Lanterna8." I copied the old vmare modules from 2.6.22.14 to 2.6.22.15 and restarted ( I guess I should be able to just give a command instead of rebooting - windows habits die hard.) VMWare server now works again.
Lanterna8 wrote -
Also, I fixed the most weird thing ever today:
My father's lappy runs ubuntu 7.10, and ran kernel 2.6.22.14 till yesterday. He upgraded to 2.6.22.15 today (old kernel is old) and vmware suddenly stopped working.
After 15 minutes fiddling with permissions, I decided to /etc/init.d/vmware-server restart (should've done it from the beginning I know) and it fails loading vmware net and vmware monitor (vmnet and vmmon modules not loaded).
Mod probe for those two says there's no such modules.
Locate vmnet showed it in /lib/modules/2.6.22.14-generic/vmware-server/vmnet.ko (wtf moment)
Anyway, 2 cp's to /lib/modules/2.6.22.15-generic/vmware-server and one reboot later, modules loaded correctly, vmware works again, and I'm thinking why the hell those weren't updated

~Lanterna8

[Goeroeboeroe]

Re: vmware-server not working after kernel update

Thanks you took the trouble to write this, but it didn't work out at all for me. In fact: I lost connection in the old kernel now too, so it apparently did do something.
I had two folders with vmware-server, one like you wrote and there's in /lib/modules a folder called 2.6.22.14-server with in it just one folder: vmware-server with in it the two files you named.
So I first only copied the one you wrote about. Same errors. Then I copied the second one and renamed it to 2.6.22.15-server.
Hooray: the script really run! Just like I remember it. And then it stopped with exactly the same error about vmnet.
I could start Windows now, so that really changed. But I got the message: Could not open /dev/vmnet8 No such device or address. So no internet.
Rebooted, removed the copied folders, rerun script, etc., but I get the same error in konsole: vmnet not loaded. Guess I'll have to go to the police tomorrow because somebody stole my vmnet.
In the old kernel I get the 'could not open /dev/vmnet8' now too.
So I'm going to reinstall vmware again and hope I'll get my network back.
Anyway, I learned quite a lot along the way. I work for about 20 years with computers, did a lot of troubleshooting with Windows. But what's really nice here: you can actually really see what you do. I mean: no secret directories with sneaky files etc.
Well, didn't work out. Next time better.

[Goeroeboeroe]

Re: vmware-server not working after kernel update

Reinstalled, booted in the old kernel and everything's working again. :P

Edit: I mean I did reinstall vmware...

[Feirefis]

Re: vmware-server not working after kernel update

As you say, it is great to be able to learn more. Worrying when I mess up something I rely on but there's always plenty of help.

Good luck with your vmware!

[Guest]

Re: vmware-server not working after kernel update

Hey folks let me hopefully show you the fix.

Open a console as root and

cd /lib/modules

ls

-you see the kernel directories

cd 2.6.22-14-generic/ [or which ever your old working kernel was]

-you see the vmware-server directory

cp -R vmware-server ../2.6.22-15-generic [or what ever your new kernel is]

cd ../2.6.22-15-generic/vmware-server

ls

-now you see you have copied the directory and its content
-the two .ko kernel module files
-no need to reboot to load modules into a running kernel

insmod vmmon.ko
insmod vmnet.ko

-now your modules are loaded but this is not enough
-you must now reconfigure the network interface

cd /usr/bin

ls vm*

-you should see the file vmware-config-network.pl so run it

./vmware-config-network.pl

-most likely you can simply accept all the default yes or no's
-then just start vmware the way you normally do.

Hope that helps

redir