Install vmware 2.0 on openSUSE 11.1

English Install/Boot/Login
1

Please accept my apologies I am very new to Linux/openSUSE.

I would like to use openSUSE as the platform to run VMWare 2.0.

I have installed openSUSE from the CD with gnome desktop and downladed vmware 2.0 and installed that also.

I have installed gcc c++ I understand that I need the Kernal-Source C header files. but cannot find them under the YAST install

Then the fun bit. running the VMWare-Config.pl

/usr/bin/vmware-config.pl

Making sure services for VMware Server are stopped.

Stopping VMware autostart virtual machines:
Virtual machines failed
Stopping VMware management services:
VMware Virtual Infrastructure Web Access
VMware Server Host Agent failed
Stopping VMware services:
VMware Authentication Daemon done
Virtual machine monitor done

None of the pre-built vmmon modules for VMware Server is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes] yes

Using compiler “/usr/bin/gcc”. Use environment variable CC to override.

Your kernel was built with “gcc” version “4.3.2”, while you are trying to use
“/usr/bin/gcc” version “4.3”. This configuration is not recommended and VMware
Server may crash if you’ll continue. Please try to use exactly same compiler as
one used for building your kernel. Do you want to go with compiler
“/usr/bin/gcc” version “4.3” anyway? [no] yes

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]

==============================================================
At this point I get totally lost as I cannot find the include files that the install is refering to.

Can anyone help. either with an answer to the above or an idiots guide to installing vmware server 2.0 on openSUSE 11.1

Thank you in advance for your help

2

did you used the live CD to install OpenSuse?
if so? i guess that the kernel source is not present so you to either to try to reinstall from a DVD and the keernel source or download the kernel with its source your self

3

The GCC4.3 is merely a warning - you can ignore it and answer YES everytime it asks for it.

You’ll need to install the kernel-source package to compile the necessary drivers, also the GCC and various other packages.

Now to accomplish this easy and fast, you should do this:
open YAST > Software Management ; Change Filter to ‘Patterns’ and select C/C++ Development and Click Accept.

Now if you like doing things from the command line, so much the better and faster to boot;
zypper install -t pattern devel_C_C++

4

Thank you for your quick reply.

The version I installed is the current version available for download on the openSUSE web site.

VMWare Server For Linux Operating Systems
Version 2.0.0|122956-10/29/08
507MB RPM Image

5

You need to install these RPMs: kernel-source, make, gcc, gcc-c++
Then you open a console and prepare with these commands:

  1. su
  2. cd /usr/src/linux
  3. make mrproper; make cloneconfig; make modules_prepare
  4. /usr/bin/vmware-config.pl

There’s a bit more on this on the following tutorial:
Install VMware server 2 in Suse / openSUSE 11 & USB support

6

I ran the zypper install as suggested - zypper install -t pattern devel_C_C++

A number of modules installed. However the install of vmware still stops at the same point:

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]

This location does not exist so I guess I am still looking at how and where do I download the correct kernel-Source C Header Files

Thank you for your replies

7

I have installed the gcc, gcc_c++ from yast. I cannot find entries for kernal-source and make.

I manually created the folder /usr/src/linux and then ran the command you suggested I half expected the result I got which was:

linux-34ub:/usr/src/linux # make mrproper; make cloneconfig; make modules_prepare
make: *** No rule to make target mrproper'. Stop. make: *** No rule to make target cloneconfig’. Stop.
make: *** No rule to make target `modules_prepare’. Stop.

I assume this is because kernel-source is still missing.

Exactly how/where do I obtain the RPMs: kernel-source and make?

8

rpm -q kernel-source

If it does not exist;
zypper in kernel-source

9

I am getting a little further with your help. Thank you

The previous commands suggested installed the kernel-source and the other missing items as follows

linux-34ub:/usr/src/linux # rpm -qa|egrep “kernel-source|gcc-|make”
gcc-c+±4.3-34.243
automake-1.10.1-4.284
make-3.81-128.14
gcc-gij-4.3-34.243
gcc-4.3-34.243
kernel-source-2.6.27.19-3.2.1
gcc-info-4.3-34.243

From the vmware-config.pl status messages it appears that the kernel requires to be built.

The path “/usr/src” is a kernel header file directory, but it does not contain
the file “linux/version.h” as expected. This can happen if the kernel has
never been built, or if you have invoked the “make mrproper” command in your
kernel directory. In any case, you may want to rebuild your kernel.

The command provided in document Install VMware server 2 in Suse / openSUSE 11 & USB support suggests:

linux-34ub:/ # make mrproper; make cloneconfig; make modules_prepare

However the status returned is:
make: *** No rule to make target mrproper'. Stop. make: *** No rule to make target cloneconfig’. Stop.
make: *** No rule to make target `modules_prepare’. Stop.

What is the correct format for this command?

10

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Browse to /usr/src/linux and then run those commands… I typically
only use:

cd /usr/src/linux
make cloneconfig && make prepare-all

Good luck.

ZenHat wrote:
> I am getting a little further with your help. Thank you
>
> The previous commands suggested installed the kernel-source and the
> other missing items as follows
>
> linux-34ub:/usr/src/linux # rpm -qa|egrep “kernel-source|gcc-|make”
> gcc-c+±4.3-34.243
> automake-1.10.1-4.284
> make-3.81-128.14
> gcc-gij-4.3-34.243
> gcc-4.3-34.243
> kernel-source-2.6.27.19-3.2.1
> gcc-info-4.3-34.243
>
> From the vmware-config.pl status messages it appears that the kernel
> requires to be built.
> ==============================================================
> The path “/usr/src” is a kernel header file directory, but it does not
> contain
> the file “linux/version.h” as expected. This can happen if the kernel
> has
> never been built, or if you have invoked the “make mrproper” command in
> your
> kernel directory. In any case, you may want to rebuild your kernel.
> ==============================================================
> The command provided in document ‘Install VMware server 2 in Suse /
> openSUSE 11 & USB support’
> (http://www.swerdna.net.au/linhowtovmwareserversuse.html) suggests:
>
> linux-34ub:/ # make mrproper; make cloneconfig; make modules_prepare
>
> However the status returned is:
> make: *** No rule to make target `mrproper’. Stop.

make: *** No rule to make target cloneconfig'. Stop. > make: *** No rule to make target modules_prepare’. Stop.
>
> What is the correct format for this command?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJJsTOGAAoJEFl00+q2r0YpzZ0QALQq6jYkiDzqjU5/FD+nvIyy
nGLvOQ5oSO9Rk3rh8buZtWmnJDgtCHT9a2mYkPhy3hzHV3aQLvEe4+wYgVOR8KEQ
BNm2xXH8WLNR30DDDkgw/cHhlAyAW5FZ9dGjwk+K8HjzTCpP2a2ldFYS9HneLKGC
uwIspn+hnEmBPUKoThx3EzkxkEvnmOFElZcSuRbEZ5x1VpssYXDSkFHZ8IRBIMQt
qsnxnORu7Rnxn3Z8oY9yus5kwdVPAANr7J7g/NhWKCHeBf4x9CuVqE5yCPPJfYSH
YWtIaRkmzq9vZTe+oOVV8Yaxkg3LCo39+UkTxStmqqFvsk5x0dgecW3R84fhJwQW
hFj3V8q1b3OZME2QOi3Oev4zvrp9NuOGmvcotLaGpLuioUJMrUssvsgprCFNjU8d
k4DKF8My2Q96Zll5SUzpGHBIPXRalFJ7dPkNXM6xP8g1FJTMzHXYfzzp/npZM+M2
OdJF6fR5U5AkRKF02sDrULEaw8HGtcvYTo3b6Uu3lUkPi+iv58a6EhI6iHjbZB4k
3v0bf6V2Ln6SA2fMIU1TUIF+I4uewlWlPYpO7hfDIeVatPoPjPL3U2yerIQX7b1W
WyqxkESJuGusQptmWsXfttMFU6I++Wzv/aBP4Fvg87tFVUcJZWh7XfkLNhd3e/bW
Ie/WQLQNq8QHQCh9+nD8
=kw8J
-----END PGP SIGNATURE-----

11

I use the commands I suggested like a parrot, without understanding. I forget where I picked them up a couple of years ago. Can you tell me what is the difference between this:

make cloneconfig && make prepare-all
and this:
make mrproper; make cloneconfig; make modules_prepare
and if mine is wrong or perhaps contains an unnecessary term, or yours is in some way better, or perhaps covers all eventualities – whatever. Interested.

Thanks

12

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, make cloneconfig as you probably know just creates a configuration
file based on your system’s current settings so the kernel you would
compile should be close to what you currently have. The mrproper…
well apparently it does some cleaning that is generally less-needed with
2.6 kernels (anything remotely current):

http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html

The prepare_all probably creates header files for everything, while make
modules_prepare probably only does modules, which is probably all you
need really. So an ideal mix may be:

cd /usr/src/linux && make cloneconfig && make modules_prepare &&
vmware_config.pl

Just a few thoughts based on Googling, though.

Good luck.

swerdna wrote:
> ab@novell.com;1953506 Wrote:
>> … I typically
>> only use:
>>
>> cd /usr/src/linux
>> make cloneconfig && make prepare-all
> I use the commands I suggested like a parrot, without understanding. I
> forget where I picked them up a couple of years ago. Can you tell me
> what is the difference between this:> make cloneconfig && make prepare-alland this:> make mrproper; make cloneconfig; make modules_prepareand if mine is wrong or perhaps contains an unnecessary term, or yours
> is in some way better, or perhaps covers all eventualities – whatever.
> Interested.
>
> Thanks
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJJsbQ/AAoJEFl00+q2r0YpFJcQAIq41s/46Dw+OdqEWIDROo64
hlJL0WLejUA5p0YK7BaCqigmTnLc1zCtGs8gyvpujVYhTDugubI/57YXc8AoJgBX
NY9mK+uZK4RIFqu8YDo1/6sfvx3nSAwGgfMdMmhiQ2sZYDLRlBz4dVWaPIrpeZNg
DUrUAGT16CmSUQ6A4Udj2TpN9tF+n+bsT91/U/65QwaoXhMEcfHjdgEX/aRTryxQ
vlTqx2zReCBuiDPTBpL1sDW8E2Tsglej3q3BK2EM20GSTdNrUqSZzcngylC+ETRW
kEvYsjfycsKs+E1ohb+1tKXzEKLlXcCwkpyl/vbSnTg4HKWihaSMZ29La6HnXsDQ
zQAJ3/sm/79dG8GTpJYKWStS4+lWiA0J5dXq9bg80oJG2XkVTIRBUcrkKLfE67En
1n7j5LnVkQKRBa6aLuYsRoD0xs3YX6kTy/AbyqIlEf5sAeZNBsrCCkoyZwnI21mh
Z0phBEAfXXbgCtBAgUMCFOLFQs2ZjJBoPvjsIgwGjraZvqJSl0nDodsqpCrTQA0L
Q6mkRtrjMXJJh7CphdBadz/SZjqh6sIJmAK54cQKlvDExAvxAwCnMPKbkAH/W8jH
yZl2THzYkdzgjauUIgdI6T1oA1RUv3O2Nerdn5UoVlRq8mKAguanJr8/gNmvj2y0
Ilr+Wu06AJq61VXu9fzN
=6jYX
-----END PGP SIGNATURE-----

13

Thanks – I’ll try it out.

14

I have been following this thread with interest. A question before putting in a sample run through on my own machine.

Is it necessary to prepare the modules from the existing compiled kernel? Also, as far as the kernel source directory is concerned, the installer usually picks it up from your installation correctly (or at least that is what I have found on the dozen or so boxes I have VMware running on).

I have found that provided you have the packages you mention installed (except for c++ - it doesn’t need that):


xxxx:~ # rpm -qa | grep gcc
libgcc43-4.3.3_20081022-9.8
libgcc43-32bit-4.3.3_20081022-9.8
gcc43-gij-4.3.3_20081022-9.2
gcc43-4.3.3_20081022-9.8
gcc-4.3-34.243
gcc-gij-4.3-34.243
xxxx:~ # rpm -qa | grep make
make-3.81-128.14
xxxx:~ # rpm -qa | grep kernel-source
kernel-source-2.6.27.19-3.2.1
xxxx:~ # rpm -qa | grep kernel
kernel-default-2.6.27.19-3.2.1
linux-kernel-headers-2.6.27-2.28
kernel-default-base-2.6.27.19-3.2.1
kernel-syms-2.6.27.19-3.2.1
kernel-default-extra-2.6.27.19-3.2.1
kernel-source-2.6.27.19-3.2.1
xxxx:~ #

Then everything tends to go through smoothly. Admittedly within the last 2-3 kernel releases there have been some errors in the header files that have cropped up but things tend to compile/work correctly for everything except for vsock. The kernel-source package you will find in the main repository (OSS) though if you do update your kernel then it will come from the Updates repo (as an aside, Fedora handles kernel-source a little differently to OpenSuSE in that supposedly you don’t need the entire kernel source present to compile modules - they have a special cut-down kernel package that is used if you do).

I would suggest that you don’t use the c/c++ devel pattern as it tends to install a lot more stuff than you really need. Also, a run through on what exactly the make commands does is present in the Makefile within /usr/src/linux (that symlinks to your current kernel’s source). There is a a whole pile of information in the makefile but if you are a non-coder then just search for the terms that are placed after the make command.

The following is a run through of the vmware-config.pl on my machine (64 bit Quad under 11.1 with the latest kernel from the updates Repo). This is for VMware 2.0 build 122956 - the latest download from the VMware website.

I find it a little odd that the compile always complains about the version of gcc that the kernel was compiled with yet the versions of gcc that come with OpenSuSE as standard are not 4.3.2 rather they are 4.3 (the main gcc) and 4.3.3 (gcc43). Perhaps the OpenSuSE kernel builders aren’t using the same one from the distribution?


xxxx:~ # vmware-config.pl                                                                         
Making sure services for VMware Server are stopped.                                                 

Stopping VMware autostart virtual machines:
   Virtual machines                                                    done
Stopping VMware management services:                                       
   VMware Virtual Infrastructure Web Access                                
   VMware Server Host Agent                                            done
Stopping VMware services:                                                  
   VMware Authentication Daemon                                        done
   Virtual machine communication interface                             done
   Virtual machine monitor                                             done
   Bridged networking on /dev/vmnet0                                   done
   Host network detection                                              done
   DHCP server on /dev/vmnet1                                          done
   Host-only networking on /dev/vmnet1                                 done
   DHCP server on /dev/vmnet8                                          done
   NAT service on /dev/vmnet8                                          done
   Host-only networking on /dev/vmnet8                                 done
   Virtual ethernet                                                    done

None of the pre-built vmmon modules for VMware Server is suitable for your 
running kernel.  Do you want this program to try to build the vmmon module for 
your system (you need to have a C compiler installed on your system)? [yes]    

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.3.2", while you are trying to use 
"/usr/bin/gcc" version "4.3". This configuration is not recommended and VMware 
Server may crash if you'll continue. Please try to use exactly same compiler as
one used for building your kernel. Do you want to go with compiler             
"/usr/bin/gcc" version "4.3" anyway? [no] yes                                  

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.27.19-3.2-default/build/include]                     

Extracting the sources of the vmmon module.
15

Looks like I have had to split the post…


Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make -C /lib/modules/2.6.27.19-3.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default'                  
make -C ../../../linux-2.6.27.19-3.2 O=/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default/. modules
  CC [M]  /tmp/vmware-config2/vmmon-only/linux/driver.o                                         
In file included from /tmp/vmware-config2/vmmon-only/./common/vmx86.h:31,                       
                 from /tmp/vmware-config2/vmmon-only/linux/driver.h:29,                         
                 from /tmp/vmware-config2/vmmon-only/linux/driver.c:101:                        
/tmp/vmware-config2/vmmon-only/./include/x86apic.h:97:1: warning: "APIC_BASE_MSR" redefined     
In file included from include2/asm/numa_64.h:5,                                                 
                 from include2/asm/numa.h:4,                                                    
                 from include2/asm/acpi.h:28,                                                   
                 from include2/asm/fixmap_64.h:15,                                              
                 from include2/asm/fixmap.h:7,                                                  
                 from include2/asm/apic.h:9,                                                    
                 from include2/asm/smp.h:13,                                                    
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/smp.h:28,                      
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/topology.h:33,                 
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/mmzone.h:687,                  
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/gfp.h:4,                       
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/kmod.h:22,                     
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/module.h:13,                   
                 from /tmp/vmware-config2/vmmon-only/./include/compat_module.h:27,              
                 from /tmp/vmware-config2/vmmon-only/linux/driver.c:26:                         
include2/asm/apicdef.h:134:1: warning: this is the location of the previous definition          
In file included from /tmp/vmware-config2/vmmon-only/./common/vmx86.h:31,                       
                 from /tmp/vmware-config2/vmmon-only/linux/driver.h:29,                         
                 from /tmp/vmware-config2/vmmon-only/linux/driver.c:101:                        
/tmp/vmware-config2/vmmon-only/./include/x86apic.h:97:1: warning: "APIC_BASE_MSR" redefined     
In file included from include2/asm/numa_64.h:5,                                                 
                 from include2/asm/numa.h:4,                                                    
                 from include2/asm/acpi.h:28,                                                   
                 from include2/asm/fixmap_64.h:15,                                              
                 from include2/asm/fixmap.h:7,                                                  
                 from include2/asm/apic.h:9,                                                    
                 from include2/asm/smp.h:13,                                                    
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/smp.h:28,                      
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/topology.h:33,                 
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/mmzone.h:687,                  
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/gfp.h:4,                       
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/kmod.h:22,                     
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/module.h:13,                   
                 from /tmp/vmware-config2/vmmon-only/./include/compat_module.h:27,              
                 from /tmp/vmware-config2/vmmon-only/linux/driver.c:26:                         
include2/asm/apicdef.h:134:1: warning: this is the location of the previous definition          
  CC [M]  /tmp/vmware-config2/vmmon-only/linux/driverLog.o                                      
  CC [M]  /tmp/vmware-config2/vmmon-only/linux/hostif.o                                         
In file included from /tmp/vmware-config2/vmmon-only/linux/hostif.c:65:                         
/tmp/vmware-config2/vmmon-only/./include/x86apic.h:97:1: warning: "APIC_BASE_MSR" redefined     
In file included from include2/asm/numa_64.h:5,                                                 
                 from include2/asm/numa.h:4,                                                    
                 from include2/asm/acpi.h:28,                                                   
                 from include2/asm/fixmap_64.h:15,                                              
                 from include2/asm/fixmap.h:7,                                                  
                 from include2/asm/apic.h:9,                                                    
                 from include2/asm/smp.h:13,                                                    
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/smp.h:28,                      
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/topology.h:33,                 
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/mmzone.h:687,                  
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/gfp.h:4,                       
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/mm.h:8,                        
                 from /tmp/vmware-config2/vmmon-only/./include/compat_page.h:23,                
                 from /tmp/vmware-config2/vmmon-only/linux/hostif.c:32:                         
include2/asm/apicdef.h:134:1: warning: this is the location of the previous definition          
  CC [M]  /tmp/vmware-config2/vmmon-only/common/comport.o                                       
  CC [M]  /tmp/vmware-config2/vmmon-only/common/cpuid.o                                         
  CC [M]  /tmp/vmware-config2/vmmon-only/common/hashFunc.o                                      
  CC [M]  /tmp/vmware-config2/vmmon-only/common/memtrack.o                                      
  CC [M]  /tmp/vmware-config2/vmmon-only/common/phystrack.o                                     
  CC [M]  /tmp/vmware-config2/vmmon-only/common/task.o                                          
  CC [M]  /tmp/vmware-config2/vmmon-only/common/vmx86.o                                         
In file included from /tmp/vmware-config2/vmmon-only/common/vmx86.h:31,                         
                 from /tmp/vmware-config2/vmmon-only/common/vmx86.c:40:                         
/tmp/vmware-config2/vmmon-only/./include/x86apic.h:97:1: warning: "APIC_BASE_MSR" redefined     
In file included from include2/asm/numa_64.h:5,                                                 
                 from include2/asm/numa.h:4,                                                    
                 from include2/asm/acpi.h:28,                                                   
                 from include2/asm/fixmap_64.h:15,                                              
                 from include2/asm/fixmap.h:7,                                                  
                 from include2/asm/apic.h:9,                                                    
                 from include2/asm/smp.h:13,                                                    
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/smp.h:28,                      
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/sched.h:68,                    
                 from /tmp/vmware-config2/vmmon-only/common/vmx86.c:32:                         
include2/asm/apicdef.h:134:1: warning: this is the location of the previous definition          
  CC [M]  /tmp/vmware-config2/vmmon-only/vmcore/moduleloop.o                                    
In file included from /tmp/vmware-config2/vmmon-only/./common/vmx86.h:31,                       
                 from /tmp/vmware-config2/vmmon-only/vmcore/moduleloop.c:35:                    
/tmp/vmware-config2/vmmon-only/./include/x86apic.h:97:1: warning: "APIC_BASE_MSR" redefined     
In file included from include2/asm/numa_64.h:5,                                                 
                 from include2/asm/numa.h:4,                                                    
                 from include2/asm/acpi.h:28,                                                   
                 from include2/asm/fixmap_64.h:15,                                              
                 from include2/asm/fixmap.h:7,                                                  
                 from include2/asm/apic.h:9,                                                    
                 from include2/asm/smp.h:13,                                                    
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/smp.h:28,                      
                 from /usr/src/linux-2.6.27.19-3.2/include/linux/sched.h:68,                    
                 from /tmp/vmware-config2/vmmon-only/./include/compat_sched.h:23,               
                 from /tmp/vmware-config2/vmmon-only/vmcore/moduleloop.c:31:                    
include2/asm/apicdef.h:134:1: warning: this is the location of the previous definition          
  LD [M]  /tmp/vmware-config2/vmmon-only/vmmon.o                                                
  Building modules, stage 2.                                                                    
  MODPOST 1 modules                                                                             
  CC      /tmp/vmware-config2/vmmon-only/vmmon.mod.o                                            
  LD [M]  /tmp/vmware-config2/vmmon-only/vmmon.ko                                               
make[1]: Leaving directory `/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default'                    
cp -f vmmon.ko ./../vmmon.o                                                                     
make: Leaving directory `/tmp/vmware-config2/vmmon-only'                                        
The vmmon module loads perfectly into the running kernel.
16

Last bit…


None of the pre-built vmci modules for VMware Server is suitable for your 
running kernel.  Do you want this program to try to build the vmci module for 
your system (you need to have a C compiler installed on your system)? [yes]   

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmci-only'
make -C /lib/modules/2.6.27.19-3.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default'                  
make -C ../../../linux-2.6.27.19-3.2 O=/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default/. modules
  CC [M]  /tmp/vmware-config2/vmci-only/linux/driver.o                                          
  CC [M]  /tmp/vmware-config2/vmci-only/linux/driverLog.o                                       
  CC [M]  /tmp/vmware-config2/vmci-only/linux/vmciKernelIf.o                                    
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciContext.o                                    
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciDatagram.o                                   
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciDriver.o                                     
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciDs.o                                         
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciEvent.o                                      
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciGroup.o                                      
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciHashtable.o                                  
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciProcess.o                                    
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciQueuePair.o                                  
  CC [M]  /tmp/vmware-config2/vmci-only/common/vmciResource.o                                   
  LD [M]  /tmp/vmware-config2/vmci-only/vmci.o                                                  
  Building modules, stage 2.                                                                    
  MODPOST 1 modules                                                                             
  CC      /tmp/vmware-config2/vmci-only/vmci.mod.o                                              
  LD [M]  /tmp/vmware-config2/vmci-only/vmci.ko                                                 
make[1]: Leaving directory `/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default'                    
cp -f vmci.ko ./../vmci.o                                                                       
make: Leaving directory `/tmp/vmware-config2/vmci-only'                                         
The vmci module loads perfectly into the running kernel.                                        

None of the pre-built vsock modules for VMware Server is suitable for your 
running kernel.  Do you want this program to try to build the vsock module for 
your system (you need to have a C compiler installed on your system)? [yes]    

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vsock-only'
make -C /lib/modules/2.6.27.19-3.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default'                  
make -C ../../../linux-2.6.27.19-3.2 O=/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default/. modules
  CC [M]  /tmp/vmware-config2/vsock-only/linux/af_vsock.o                                       
  CC [M]  /tmp/vmware-config2/vsock-only/linux/driverLog.o                                      
  CC [M]  /tmp/vmware-config2/vsock-only/linux/util.o                                           
  CC [M]  /tmp/vmware-config2/vsock-only/linux/vsockAddr.o                                      
  LD [M]  /tmp/vmware-config2/vsock-only/vsock.o                                                
  Building modules, stage 2.                                                                    
  MODPOST 1 modules                                                                             
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config2/vsock-only/vsock.ko] undefined!          
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config2/vsock-only/vsock.ko] undefined!         
WARNING: "VMCI_GetContextID" [/tmp/vmware-config2/vsock-only/vsock.ko] undefined!               
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config2/vsock-only/vsock.ko] undefined!               
  CC      /tmp/vmware-config2/vsock-only/vsock.mod.o                                            
  LD [M]  /tmp/vmware-config2/vsock-only/vsock.ko                                               
make[1]: Leaving directory `/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default'                    
cp -f vsock.ko ./../vsock.o                                                                     
make: Leaving directory `/tmp/vmware-config2/vsock-only'                                        
Unable to make a vsock module that can be loaded in the running kernel:                         
insmod: error inserting '/tmp/vmware-config2/vsock.o': -1 Unknown symbol in module              
There is probably a slight difference in the kernel configuration between the                   
set of C header files you specified and your running kernel.  You may want to                   
rebuild a kernel based on that directory, or specify another directory.                         

The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and   
host.  The rest of this software provided by VMware Server is designed to work 
independently of this feature.  If you wish to have the VSOCK feature  you can 
install the driver by running vmware-config.pl again after making sure that    
gcc, binutils, make and the kernel sources for your running kernel are         
installed on your machine. These packages are available on your distribution's 
installation CD.                                                               
 Press the Enter key to continue.]                                            

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes]                                                                 

None of the pre-built vmnet modules for VMware Server is suitable for your 
running kernel.  Do you want this program to try to build the vmnet module for 
your system (you need to have a C compiler installed on your system)? [yes]    

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config3/vmnet-only'
make -C /lib/modules/2.6.27.19-3.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default'                  
make -C ../../../linux-2.6.27.19-3.2 O=/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default/. modules
  CC [M]  /tmp/vmware-config3/vmnet-only/driver.o                                               
  CC [M]  /tmp/vmware-config3/vmnet-only/hub.o                                                  
  CC [M]  /tmp/vmware-config3/vmnet-only/userif.o                                               
  CC [M]  /tmp/vmware-config3/vmnet-only/netif.o                                                
  CC [M]  /tmp/vmware-config3/vmnet-only/bridge.o                                               
  CC [M]  /tmp/vmware-config3/vmnet-only/filter.o                                               
  CC [M]  /tmp/vmware-config3/vmnet-only/procfs.o                                               
  CC [M]  /tmp/vmware-config3/vmnet-only/smac_compat.o                                          
  CC [M]  /tmp/vmware-config3/vmnet-only/smac.o                                                 
  CC [M]  /tmp/vmware-config3/vmnet-only/vnetEvent.o                                            
  CC [M]  /tmp/vmware-config3/vmnet-only/vnetUserListener.o                                     
  LD [M]  /tmp/vmware-config3/vmnet-only/vmnet.o                                                
  Building modules, stage 2.                                                                    
  MODPOST 1 modules                                                                             
  CC      /tmp/vmware-config3/vmnet-only/vmnet.mod.o                                            
  LD [M]  /tmp/vmware-config3/vmnet-only/vmnet.ko                                               
make[1]: Leaving directory `/usr/src/linux-2.6.27.19-3.2-obj/x86_64/default'                    
cp -f vmnet.ko ./../vmnet.o                                                                     
make: Leaving directory `/tmp/vmware-config3/vmnet-only'                                        
The vmnet module loads perfectly into the running kernel.                                       

Please specify a port for remote connections to use [xxx] 

Using Existing SSL Certificate.
You have a pre-existing config.xml.  The new version will be created as 
/etc/vmware/hostd/NEW_config.xml.  Please check the new file for any new values
that you may need to migrate to your current config.xml.                       

Do you want to use the current proxy port values? [yes] 

The current administrative user for VMware Server  is 'xxxx'.  Would you like 
to specify a different administrator? [no]                                    

Using xxxx as the VMware Server administrator.

You have a pre-existing authorization.xml.  The new version will be created as 
/etc/vmware/hostd/NEW_authorization.xml.  Please check the new file for any new
values that you may need to migrate to your current authorization.xml.         

You have a pre-existing vmInventory.xml.  The new version will be created as 
/etc/vmware/hostd/NEW_vmInventory.xml.  Please check the new file for any new 
values that you may need to migrate to your current vmInventory.xml.          

You have a pre-existing clients.xml.  The new version will be created as 
/usr/lib/vmware/hostd/docroot/client/NEW_clients.xml.  Please check the new 
file for any new values that you may need to migrate to your current        
clients.xml.                                                                

This program previously created the file 
/usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.16/work, and was about to 
remove it.  Somebody else apparently did it already.                         

insserv: script vmware-autostart: service VMware already provided!
insserv: script vmware-mgmt: service VMware already provided!
insserv: script vmware-core: service VMware already provided!
In which directory do you want to keep your virtual machine files?
[/local/vmare/Virtual_Machines]

The path "/local/vmare/Virtual_Machines" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]

You have a pre-existing datastores.xml.  The new version will be created as
/etc/vmware/hostd/NEW_datastores.xml.  Please check the new file for any new
values that you may need to migrate to your current datastores.xml.

Do you want to enter a serial number now? (yes/no/help) [no]

Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                             done
   Virtual ethernet                                                    done
   Bridged networking on /dev/vmnet0                                   done
   Host-only networking on /dev/vmnet1 (background)                    done
   DHCP server on /dev/vmnet1                                          done
   Host-only networking on /dev/vmnet8 (background)                    done
   DHCP server on /dev/vmnet8                                          done
   NAT service on /dev/vmnet8                                          done
   VMware Server Authentication Daemon (background)                    done
   Shared Memory Available                                             done
Starting VMware management services:
   VMware Server Host Agent (background)                               done
   VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
   Virtual machines                                                    done

The configuration of VMware Server 2.0.0 build-122956 for Linux for this
running kernel completed successfully.

xxxx:~ #
17

“Is it necessary to prepare the modules from the existing compiled kernel?”

I’m curious. Did you get an answer to this? I’m presuming you were wondering if the pre-compiled kernel has the real-time clock compiled and CONFIG_PARPORT_PC loaded as a module? Better yet, can someone here tell me how I would find out for myself?

Thanks!

18

No, I haven’t got an answer just yet as far as the necessity to prepare the kernel source before the modules are compiled for VMware. In all of the boxes I have run VMware (under SuSE - OpenSuSE and SLES) I have not found it necessary; however, that view may change depending on whether someone could add to the errors that I am getting in running through the vmware-config.pl routine that I pasted in beforehand.

Not to hijack the thread about other kernel issues (it is supposed to be on VMware) but to answer your questions (correct me if I am wrong):

  1. I don’t think that the real-time modules are compiled in by default. The reason why I say this is the of you want to run any audio applications (e.g. Rosegarden) then you usually need to bring down the clock resolution from what the default kernel sets it to under OpenSuSE and add the real time modules as well. This is a PITA as rather than having one box that is capable of doing everything (unless you are really into kernel compilation) you would need to have a dedicated machine for audio things, hence the availability of projects like JackLab and 64Studio. Oh, and the real time stuff relies on the running kernel and anything under it - so you may run into difficulties running real time within a VMware session running on a non-real time box (though this isn’t the sort of thing that I would do).

  2. Parallel port support is compiled as a module and is definitely available as standard under the normal OpenSuSE kernel (including all of the options for ECP/EPP, etc.). Have a look at the README.SUSE in /usr/src/linux about pulling the current kernel configuration (make sure you have “kernel-source” installed). It seems that running a “make cloneconfig” will pull together the current running kernel setup from /proc for you. Read through the file, it will explain in detail how it all works. I am not on my 64 bit box at the moment but under 32 bit it seems that the .config is located in /usr/src/linux-obj/i586/default (presumably x86_64 for 64 bit).

Would really like an answer to the first question though… :slight_smile:

19

Hi folks,

I am having the same difficulties. I am using SuSE 11.1 x86_64 on AMD Opteron with two dual processors. I get the same gcc mismatch error message as the others. When I ignore the gcc warning and follow through all of the prompts of vmware-config.pl, I receive the success message, “*The configuration of VMware Server 2.0.0 build-122956 for Linux for this running kernel completed successfully.
*,” but when I try to open vmware with either 127.0.0.1:8222 or …:8333 in firefox, I get the “503 Service Unavailable” error message.

I tried Swerda’s instructions provided in this post and more detailed in Install VMware server 2 in Suse / openSUSE 11 & USB support, but I still receive the same gcc mismatch error and the 503 error.

Has anyone had success moving beyond this point?

Cheers,

Joe from Silver Spring, MD

20

Check this thread Joe. It suggest adding the address:

127.0.0.1 localhost
to /etc/hosts
Thread: VMware Communities: 503 Service Unavailable - VMWare Server …
And others in that thread suggest to disable IPv6 and to re-run vmware-config.pl. Some things to check.