Does this mean that we do not have to "save" vmnet.o and vm-somethin.o from the 144 version, as suggested in an ealier post? Dimitris On Thursday 29 January 2004 14:32, Alex Angerhofer wrote:

On Thu, 29 Jan 2004, David Bottrill wrote:

...

On Thursday 29 January 2004 20:51, Luis-Miguel Astudillo wrote:

...

Has anyone installed VMWare v4.0 on Suse 9.0 and if successfull what are the steps.

Luis,

There have been a lot of posts regarding this in the past, and there have been a number of solutions. The one that worked for me is as follows:

Firstly make sure you have the kernel source installed along with GCC, YAST should sort out any dependencies. I'm not sure if this is really required but goto /usr/src/linux and as root run the following commands:

make cloneconfig make dep

Go to http://kerneltrap.org/node/view/1804

Here there is information on installing VMWare on the 2.6 kernel using a patch called any-any-update.

Follow the instructions and you will find VMWare works extremely well. If you have the 2.4.21-166 updated kernel using Yast Online Update, make sure you have also installed the updated kernel source from SuSE.

and don't forget to *not* install the vmware modules that came with vmware when you run the vmware-config.pl script, or if it does that automatically, replace them with your own freshly compiled ones.

Alex.

On Saturday 31 January 2004 11:11, Alex Angerhofer wrote:

AFAIK there is no vmxxx.o that comes with the update kernel. There is only the sources for these objects and that comes with the CD set as km_vmware. Thus, when you follow David's instructions, you will end up compiling the modules with the new kernel in place. At that point you can then setup vmware provided that you don't replace the newly compiled modules with their shipped ones (or the ones that had been previously compiled with a different kernel in place). In other words, you have to make sure that you use the newly compiled modules or else the kernel will not like them.

Cheers, Alex.

Thanx Alex, much appreciate your help. Sooo, should I remove these modules, bring in the 166 Kernel, then reinsert Km_vmare, then try to see if i can reinstall vmware without over-writing the suse supplied vmxxx.o modules? tia Dimitris

On Sat, 31 Jan 2004, plain wrote:

...

Does this mean that we do not have to "save" vmnet.o and vm-somethin.o from the 144 version, as suggested in an ealier post? Dimitris

On Thursday 29 January 2004 14:32, Alex Angerhofer wrote:

...

On Thu, 29 Jan 2004, David Bottrill wrote:

...

On Thursday 29 January 2004 20:51, Luis-Miguel Astudillo wrote:

...

Has anyone installed VMWare v4.0 on Suse 9.0 and if successfull what are the steps.

Luis,

There have been a lot of posts regarding this in the past, and there have been a number of solutions. The one that worked for me is as follows:

Firstly make sure you have the kernel source installed along with GCC, YAST should sort out any dependencies. I'm not sure if this is really required but goto /usr/src/linux and as root run the following commands:

make cloneconfig make dep

Go to http://kerneltrap.org/node/view/1804

Here there is information on installing VMWare on the 2.6 kernel using a patch called any-any-update.

Follow the instructions and you will find VMWare works extremely well. If you have the 2.4.21-166 updated kernel using Yast Online Update, make sure you have also installed the updated kernel source from SuSE.

and don't forget to *not* install the vmware modules that came with vmware when you run the vmware-config.pl script, or if it does that automatically, replace them with your own freshly compiled ones.

Alex.

On Sun, 1 Feb 2004, plain wrote:

On Saturday 31 January 2004 11:11, Alex Angerhofer wrote:

...

AFAIK there is no vmxxx.o that comes with the update kernel. There is only the sources for these objects and that comes with the CD set as km_vmware. Thus, when you follow David's instructions, you will end up compiling the modules with the new kernel in place. At that point you can then setup vmware provided that you don't replace the newly compiled modules with their shipped ones (or the ones that had been previously compiled with a different kernel in place). In other words, you have to make sure that you use the newly compiled modules or else the kernel will not like them.

Cheers, Alex.

Thanx Alex, much appreciate your help. Sooo, should I remove these modules, bring in the 166 Kernel, then reinsert Km_vmare, then try to see if i can reinstall vmware without over-writing the suse supplied vmxxx.o modules? tia Dimitris

The way I solved the problem here is basically this: 1.) Install km_vmware and the default kernel sources with YaST2 2.) Update the kernel to the latest version (either 9.0 stock or the later default kernel via YOU) 3.) make sure that VMWare is stopped: /etc/init.d/vmware stop 4.) Make dep in the kernel source tree: cd /usr/src ln -s linux-2.4.xxx linux cd linux make cloneconfig make dep && clean 5.) Recompile the VMWare kernel modules cd /usr/src/kernel-modules/vmware make -f Makefile.module make -f Makefile.module install save the object files that are generated by this step in /usr/src/kernel-modules/vmware in a save place for later use 6.) Run vmware-config.pl If it allows you to skip the compile step for the vmmon and vmnet modules do that. If it insists on carrying out that step, let it have its will, then later on copy the saved modules into their proper place in /usr/src/kernel-modules/vmware This should do the trick. By the way, alt.linux.suse is full with contributions to the subject. Thus, a google search will unearth lots of variations on the theme. Best regards, Alex.

On Fri, 2004-01-30 at 04:56, David Bottrill wrote:

kbonasia@mclink.net said:

...

yes, download vmware and next as root start the vmware-config.pl,

say "no"

...

when it ask if you desire to "update" the vmnet modules (first install the right kernel patch for vmware, from Yast...), then, login as user and write vmware &... then ... insert the right serial code (trial or buy...) and go!

This does not work is you have an Athlon Kernel that you have updated online using YAST. If you are running the 2.4.21-199 kernel this does not work as SuSE have not provided VMWare drivers with this kernel and if you allow vmware to compile it's own kernel modules they will fail. The any-any-update is the best way to get VMWare running.

Using the k_deflt kernel for intel I have been able to use the modules from the 121 kernel with the 166 kernel. Install the 121 kernel copy the modules from /lib/modules/2.4.21-121-default/misc/ to someplace safe install the newer kernel copy the modules back to /lib/modules/2.4.21-121-default/misc/ run depmod -a run vmware-config.pl -but- do not over right the modules. If the config program does overwrite the modules run /etc/init.d/vmware stop, copy the modules again and then /etc/init.d/vmware start. run vmware I have done this successfully on three different boxes without problem. I have also found that after the initial configuration of vmware if you have a problem and it wants to force you to run the configuration program look in /etc/vmware for a file called not-installed and delete it. You should be able to start the vmware processes after that. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)