Ever been frustrated with getting VMware Server 2.02 to work on a 2.6.37 kernel - I sure did, and here is the craziness to get it to work.
Remove any lingering modules:
-
AwesomO:~/Downloads # rm -rf /usr/lib/vmware/modules/source*
Run a directory listing - note that the RPMs VMware-server and vmware-fix-workstation are listed. The fix was gotten from here: http://software.opensuse.org/search/download?base=ALL&file=home:/malcolmlewis:/Testing/openSUSE_11.4/noarch/vmware-fix-workstation-6.5.5-1.0-1.1.noarch.rpm&query=vmware-fix-workstation
-
AwesomO:~/Downloads # ls
-
VMware-server-2.0.2-203138.i386.rpm
-
vmware-fix-workstation-6.5.5-1.0-1.1.noarch.rpm
-
AwesomO:~/Downloads # rpm -Uvh VMware-server-2.0.2-203138.i386.rpm
-
Preparing... ########################################### [100%]
-
1:VMware-server ########################################### [100%]
-
-
The installation of VMware Server 2.0.2 for Linux completed successfully.
-
You can decide to remove this software from your system at any time by
-
invoking the following command: "rpm -e VMware-server".
-
-
Before running VMware Server for the first time, you need to
-
configure it for your running kernel by invoking the
-
following command: "/usr/bin/vmware-config.pl".
-
-
Enjoy,
-
-
--the VMware team
Now we need to run the first part of fix:
-
AwesomO:~/Downloads # rpm -Uvh
-
VMware-server-2.0.2-203138.i386.rpm
-
vmware-fix-1.3-1.1.noarch.rpm
-
vmware-fix-workstation-6.5.5-1.0-1.1.noarch.rpm
-
AwesomO:~/Downloads # rpm -Uvh vmware-fix-workstation-6.5.5-1.0-1.1.noarch.rpm
-
Preparing... ########################################### [100%]
-
1:vmware-fix-workstation-########################################### [100%]
-
AwesomO:~/Downloads # /usr/sbin/vmware_
-
vmware_update_softlinks vmware_workstation_fix
-
AwesomO:~/Downloads # /usr/sbin/vmware_workstation_fix
-
Creating backup files
-
Directory exists
-
patching file vmci-only/include/compat_semaphore.h
-
patching file vmci-only/include/pgtbl.h
-
patching file vmmon-only/include/compat_semaphore.h
-
patching file vmmon-only/linux/driver.c
-
Hunk #1 succeeded at 168 (offset -1 lines).
-
Hunk #2 succeeded at 420 (offset -1 lines).
-
Hunk #3 succeeded at 2408 (offset -1 lines).
-
Hunk #4 succeeded at 2441 (offset -1 lines).
-
patching file vmmon-only/linux/hostif.c
-
patching file vmnet-only/compat_semaphore.h
-
patching file vmnet-only/vnetFilter.h
-
patching file vmnet-only/vnetUserListener.c
-
patching file vsock-only/linux/af_vsock.c
-
Hunk #1 succeeded at 3149 (offset -39 lines).
-
Hunk #2 succeeded at 3172 (offset -39 lines).
-
Hunk #3 succeeded at 3184 (offset -39 lines).
-
Hunk #4 succeeded at 3244 (offset -39 lines).
-
Hunk #5 succeeded at 3260 (offset -39 lines).
-
Hunk #6 succeeded at 3294 (offset -39 lines).
-
Hunk #7 succeeded at 3391 (offset -39 lines).
-
Hunk #8 succeeded at 3992 (offset -49 lines).
-
Hunk #9 succeeded at 4031 (offset -49 lines).
-
Hunk #10 succeeded at 4114 (offset -49 lines).
-
Hunk #11 succeeded at 4337 (offset -49 lines).
-
Hunk #12 succeeded at 4380 (offset -49 lines).
-
Hunk #13 succeeded at 4472 (offset -49 lines).
-
patching file vsock-only/linux/af_vsock.h
-
/usr/sbin/vmware_workstation_fix: line 46: /usr/bin/vmware-modconfig: No such file or directory
Now we need to use Yast to install the VMware-server fix, but we need to remove the Workstation one - this is after it was ran and broke - crazy? I know!!!
-
AwesomO:~/Downloads # yast
Now run the vmware_server_fix and allow the patch to run - note: if you make a mistake on any setting you need to start all over and remove all of the RPMs
-
AwesomO:~/Downloads # /usr/sbin/
-
Display all 382 possibilities? (y or n)
-
AwesomO:~/Downloads # /usr/sbin/vmware_
-
vmware_server_fix vmware_update_softlinks vmware_workstation_fix
-
AwesomO:~/Downloads # /usr/sbin/vmware_server_fix
-
Restoring backup
-
Creating backup files
-
Directory exists
-
patching file vmci-only/include/pgtbl.h
-
Reversed (or previously applied) patch detected! Assume -R? [n]
-
Apply anyway? [n]
-
Skipping patch.
-
1 out of 1 hunk ignored -- saving rejects to file vmci-only/include/pgtbl.h.rej
-
patching file vmnet-only/vnetUserListener.c
-
Reversed (or previously applied) patch detected! Assume -R? [n]
-
Apply anyway? [n]
-
Skipping patch.
-
1 out of 1 hunk ignored -- saving rejects to file vmnet-only/vnetUserListener.c.rej
-
patching file vmci-only/Makefile
-
patching file vmmon-only/common/vmx86.c
-
patching file vmmon-only/include/compat_cred.h
-
patching file vmmon-only/include/x86svm.h
-
patching file vmmon-only/linux/driver.c
-
Hunk #1 succeeded at 1982 (offset -2 lines).
-
patching file vmmon-only/linux/hostif.c
-
Hunk #4 succeeded at 3451 (offset -8 lines).
-
Hunk #5 succeeded at 3575 (offset -8 lines).
-
patching file vmmon-only/Makefile
-
patching file vmnet-only/Makefile
-
patching file vmnet-only/netif.c
-
patching file vsock-only/Makefile
-
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
-
-
You must read and accept the End User License Agreement to continue.
-
Press enter to display it.
-
-
-
Do you accept? (yes/no) yes
-
-
Thank you.
-
-
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.5.1", while you are trying to use
-
"/usr/bin/gcc" version "4.5". 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.5" anyway? [no] yes
-
-
What is the location of the directory of C header files that match your running
-
kernel? [/lib/modules/2.6.37.6-0.5-desktop/build/include]
-
-
-
-
-
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.]
-
-
Do you want networking for your virtual machines? (yes/no/help) [yes]
-
-
Configuring a bridged network for vmnet0.
-
-
Please specify a name for this network.
-
[Bridged]
-
-
Your computer has multiple ethernet network interfaces available: eth0, eth1.
-
Which one do you want to bridge to vmnet0? [eth0]
-
-
The following bridged networks have been defined:
-
-
Do you wish to configure another bridged network? (yes/no) [no] yes
-
-
Configuring a bridged network for vmnet2.
-
-
Please specify a name for this network.
-
[Bridged]
-
-
The following bridged networks have been defined:
-
-
All your ethernet interfaces are already bridged.
-
-
Do you want to be able to use NAT networking in your virtual machines? (yes/no)
-
[yes] no
-
-
Do you want to be able to use host-only networking in your virtual machines?
-
[no] no
-
-
Network name "Bridged" for vmnet2 is already in use by vmnet0 -- renaming to
-
"Bridged (2)"
-
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-config5/vmnet-only'
-
make -C /lib/modules/2.6.37.6-0.5-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
-
make[1]: Entering directory `/usr/src/linux-2.6.37.6-0.5-obj/i386/desktop'
-
make -C ../../../linux-2.6.37.6-0.5 O=/usr/src/linux-2.6.37.6-0.5-obj/i386/desktop/. modules
-
CC [M] /tmp/vmware-config5/vmnet-only/driver.o
-
CC [M] /tmp/vmware-config5/vmnet-only/hub.o
-
CC [M] /tmp/vmware-config5/vmnet-only/userif.o
-
CC [M] /tmp/vmware-config5/vmnet-only/netif.o
-
CC [M] /tmp/vmware-config5/vmnet-only/bridge.o
-
CC [M] /tmp/vmware-config5/vmnet-only/filter.o
-
CC [M] /tmp/vmware-config5/vmnet-only/procfs.o
-
CC [M] /tmp/vmware-config5/vmnet-only/smac_compat.o
-
CC [M] /tmp/vmware-config5/vmnet-only/smac.o
-
CC [M] /tmp/vmware-config5/vmnet-only/vnetEvent.o
-
CC [M] /tmp/vmware-config5/vmnet-only/vnetUserListener.o
-
LD [M] /tmp/vmware-config5/vmnet-only/vmnet.o
-
Building modules, stage 2.
-
MODPOST 1 modules
-
CC /tmp/vmware-config5/vmnet-only/vmnet.mod.o
-
LD [M] /tmp/vmware-config5/vmnet-only/vmnet.ko
-
make[1]: Leaving directory `/usr/src/linux-2.6.37.6-0.5-obj/i386/desktop'
-
cp -f vmnet.ko ./../vmnet.o
-
make: Leaving directory `/tmp/vmware-config5/vmnet-only'
-
The vmnet module loads perfectly into the running kernel.
-
-
Please specify a port for remote connections to use [902]
-
-
Please specify a port for standard http connections to use [8222]
-
-
Please specify a port for secure http (https) connections to use [8333]
-
-
The current administrative user for VMware Server is ''. Would you like to
-
specify a different administrator? [no]
-
-
Using root as the VMware Server administrator.
-
-
insserv: Service network is missed in the runlevels 2 to use service VMware
-
In which directory do you want to keep your virtual machine files?
-
[/var/lib/vmware/Virtual Machines] /virtual_machines
-
-
The path "/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.
-
-
Please enter your 20-character serial number.
-
-
Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel: YOURKEY
-
-
Creating a new VMware VIX API installer database using the tar4 format.
-
-
Installing VMware VIX API.
-
-
In which directory do you want to install the VMware VIX API binary files?
-
[/usr/bin]
-
-
In which directory do you want to install the VMware VIX API library files?
-
[/usr/lib/vmware-vix/lib]
-
-
The path "/usr/lib/vmware-vix/lib" does not exist currently. This program is
-
going to create it, including needed parent directories. Is this what you want?
-
[yes]
-
-
In which directory do you want to install the VMware VIX API document pages?
-
[/usr/share/doc/vmware-vix]
-
-
The path "/usr/share/doc/vmware-vix" does not exist currently. This program is
-
going to create it, including needed parent directories. Is this what you want?
-
[yes]
-
-
The installation of VMware VIX API 1.6.2 build-203138 for Linux completed
-
successfully. You can decide to remove this software from your system at any
-
time by invoking the following command: "/usr/bin/vmware-uninstall-vix.pl".
-
-
Enjoy,
-
-
--the VMware team
-
-
Starting VMware services:
-
Virtual machine monitor done
-
Virtual machine communication interface done
-
Virtual ethernet done
-
Bridged networking on /dev/vmnet0 done
-
Bridged networking on /dev/vmnet2 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.2 build-203138 for Linux for this
-
running kernel completed successfully.
And now check your firewall rules and logon to the VMware server webconsole in IE or Chrome - at the time of this writing Firefox was not working.
Additional Resources
http://forums.opensuse.org/english/get-technical-help-here/applications/453529-cannot-find-kernel-sources-2.html
http://en.opensuse.org/SDB:Installing_VMware_server_or_workstation
Comments
Confirmed to work on 64 Bit
Submitted by Anonymous (not verified) on
Dear Ron,
Thank you very much for the solution.
You are 100% right, It is the only way to go:
1.) run workstation fix
2.) then run server fix
I can confirm that this is also working on a 64 Bit version
I have OpenSUSE 11.4 (2.6.37.6-0.5-default) and used VMware-server-2.0.2-203138.x86_64.rpm
Ohter issues:
"VMware Infrastructure Web Access" won't work on Firefox 4.0, 5.0 or Konqueror.
I go it work on Opera, but it takes time to load.
Otherwise:
You can try VirtualBox.
Just use VNC over ssh to have decent speed.
Many thanks!!!
Glad it worked
Submitted by admin on
Virtualbox is a pretty nice toy, but in some environment's VMware will be always picked over an alternative. Virtualbox does have great 3d acceleration though - I tested it with a 2 million polygon teapot in 3DSMax with a 360' degree rotation AND had NO lag :)
I have also heard that the latest CentOS installs vmware server easily and you can also get around the Firefox issue partially by enabling the older version of SSL in about:config.
Ron
Me Ef
Submitted by Anonymous (not verified) on
Hey guys I'm trying the same with kernel-default 2.6.37.6-0.5 on suse 11.4 the 64bit version
so your help has been precious (sorry for my english)
now I meet another problem building vsock module ... (conseguently also vmnet module fails)
####################################
Building the vsock module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config14/vsock-only'
make -C /lib/modules/2.6.37.6-0.5-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.37.6-0.5-obj/x86_64/default'
make -C ../../../linux-2.6.37.6-0.5 O=/usr/src/linux-2.6.37.6-0.5-obj/x86_64/default/. modules
CC [M] /tmp/vmware-config14/vsock-only/linux/af_vsock.o
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:340:4: warning: initialization from incompatible pointer type
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:424:8: warning: type defaults to ‘int’ in declaration of ‘DECLARE_MUTEX’
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:424:1: warning: parameter names (without types) in function declaration
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmci_GetAFValue’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:534:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:534:10: note: each undeclared identifier is reported only once for each function it appears in
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘__VSockVmciCreate’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:2437:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciSkDestruct’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:2614:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciPoll’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:3394:22: error: ‘struct sock’ has no member named ‘sk_sleep’
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciDevOpen’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:4689:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciDevRelease’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:4717:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciExit’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:4887:10: error: ‘registrationMutex’ undeclared (first use in this function)
make[4]: *** [/tmp/vmware-config14/vsock-only/linux/af_vsock.o] Error 1
make[3]: *** [_module_/tmp/vmware-config14/vsock-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.37.6-0.5-obj/x86_64/default'
make: *** [vsock.ko] Error 2
make: Leaving directory `/tmp/vmware-config14/vsock-only'
Unable to build the vsock module.
########################
Sombody have ideas??
I don't know what to do with pointers & arrays
where have u downloaded the vmware-server-fix?
the trick with vmware-workstation-fix seems to work good (maybe a better solution)
Many Thanks 'till here
any good
Efrem
me Ef
Submitted by Anonymous (not verified) on
Hey guys I'm trying the same with kernel-default 2.6.37.6-0.5 on suse 11.4 the 64bit version
so your help has been precious (sorry for my english)
now I meet another problem building vsock module ... (conseguently also vmnet module fails)
####################################
Building the vsock module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config14/vsock-only'
make -C /lib/modules/2.6.37.6-0.5-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.37.6-0.5-obj/x86_64/default'
make -C ../../../linux-2.6.37.6-0.5 O=/usr/src/linux-2.6.37.6-0.5-obj/x86_64/default/. modules
CC [M] /tmp/vmware-config14/vsock-only/linux/af_vsock.o
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:340:4: warning: initialization from incompatible pointer type
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:424:8: warning: type defaults to ‘int’ in declaration of ‘DECLARE_MUTEX’
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:424:1: warning: parameter names (without types) in function declaration
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmci_GetAFValue’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:534:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:534:10: note: each undeclared identifier is reported only once for each function it appears in
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘__VSockVmciCreate’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:2437:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciSkDestruct’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:2614:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciPoll’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:3394:22: error: ‘struct sock’ has no member named ‘sk_sleep’
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciDevOpen’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:4689:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciDevRelease’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:4717:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config14/vsock-only/linux/af_vsock.c: In function ‘VSockVmciExit’:
/tmp/vmware-config14/vsock-only/linux/af_vsock.c:4887:10: error: ‘registrationMutex’ undeclared (first use in this function)
make[4]: *** [/tmp/vmware-config14/vsock-only/linux/af_vsock.o] Error 1
make[3]: *** [_module_/tmp/vmware-config14/vsock-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.37.6-0.5-obj/x86_64/default'
make: *** [vsock.ko] Error 2
make: Leaving directory `/tmp/vmware-config14/vsock-only'
Unable to build the vsock module.
########################
Sombody have ideas??
I don't know what to do with pointers & arrays
where have u downloaded the vmware-server-fix?
the trick with vmware-workstation-fix seems to work good (maybe a better solution)
Many Thanks 'till here
any good
Efrem
help ...me Ef
Submitted by Anonymous (not verified) on
thanks guys this seams to work great.. with both
- kernel-2.6.37.6-0.5-default
- kernel-2.6.37.6-0.5-desktop
I'm using ...
- VMware-server-2.0.2-203138.x86_64.rpm
- vmware-fix-workstation-6.5.5-1.0-1.1.noarch.rpm
now it fails to build vmsock module (so even vmnet module fail aborting the entire installation)
this is the log:
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-config22/vsock-only'
make -C /lib/modules/2.6.37.6-0.5-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.37.6-0.5-obj/x86_64/desktop'
make -C ../../../linux-2.6.37.6-0.5 O=/usr/src/linux-2.6.37.6-0.5-obj/x86_64/desktop/. modules
CC [M] /tmp/vmware-config22/vsock-only/linux/af_vsock.o
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:340:4: warning: initialization from incompatible pointer type
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:424:8: warning: type defaults to ‘int’ in declaration of ‘DECLARE_MUTEX’
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:424:1: warning: parameter names (without types) in function declaration
/tmp/vmware-config22/vsock-only/linux/af_vsock.c: In function ‘VSockVmci_GetAFValue’:
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:534:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:534:10: note: each undeclared identifier is reported only once for each function it appears in
/tmp/vmware-config22/vsock-only/linux/af_vsock.c: In function ‘__VSockVmciCreate’:
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:2437:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config22/vsock-only/linux/af_vsock.c: In function ‘VSockVmciSkDestruct’:
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:2614:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config22/vsock-only/linux/af_vsock.c: In function ‘VSockVmciPoll’:
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:3394:22: error: ‘struct sock’ has no member named ‘sk_sleep’
/tmp/vmware-config22/vsock-only/linux/af_vsock.c: In function ‘VSockVmciDevOpen’:
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:4689:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config22/vsock-only/linux/af_vsock.c: In function ‘VSockVmciDevRelease’:
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:4717:10: error: ‘registrationMutex’ undeclared (first use in this function)
/tmp/vmware-config22/vsock-only/linux/af_vsock.c: In function ‘VSockVmciExit’:
/tmp/vmware-config22/vsock-only/linux/af_vsock.c:4887:10: error: ‘registrationMutex’ undeclared (first use in this function)
make[4]: *** [/tmp/vmware-config22/vsock-only/linux/af_vsock.o] Error 1
make[3]: *** [_module_/tmp/vmware-config22/vsock-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.37.6-0.5-obj/x86_64/desktop'
make: *** [vsock.ko] Error 2
make: Leaving directory `/tmp/vmware-config22/vsock-only'
Unable to build the vsock module.
vmware-hostd SEGFAULT
Submitted by Anonymous (not verified) on
On my 64 bit openSuSE vmware-hostd kept crashing when adding an existing VM to inventory. Same happend at startup of vmware after a new VM was created.
Solution:
cd /usr/lib/vmware/lib/libxml2.so.2
mv libxml2.so.2 SKIP_libxml2.so.2
vmware fix error
Submitted by Anonymous (not verified) on
Hi guys:
When I run vmware-fix y have the following error:
Warning: vmware-fix-1.3-1.1.noarch.rpm: Header V3 DSA/SHA1 signature. key ID: d83ee527: NOKEY
error: Failed dependencies:
patch is needed by vmware-fix-1.3-1.1.noarch
Could you help me with this?
vmware_server_fix error
Submitted by Anonymous (not verified) on
Hi
When I run vmware_server_fix have following error:
----------
linux-xtpo:/usr/src/linux/include/linux # vmware_server_fix
Restoring backup
Creating backup files
Directory exists
compat_cred.h exists, removing
patching file vmci-only/include/pgtbl.h
patching file vmnet-only/vnetUserListener.c
patching file vmci-only/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file vmmon-only/common/vmx86.c
patching file vmmon-only/include/compat_cred.h
patching file vmmon-only/include/x86svm.h
patching file vmmon-only/linux/driver.c
patching file vmmon-only/linux/hostif.c
patching file vmmon-only/Makefile
patching file vmnet-only/Makefile
patching file vmnet-only/netif.c
patching file vsock-only/Makefile
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]
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
Your kernel was built with "gcc" version "4.5.1", while you are trying to use
"/usr/bin/gcc" version "4.5". 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.5" anyway? [no] yes
What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.37.6-0.7'
WARNING: Symbol version dump /usr/src/linux-2.6.37.6-0.7/Module.symvers
is missing; modules will have no dependencies and modversions.
CC [M] /tmp/vmware-config2/vmmon-only/linux/driverLog.o
In file included from /tmp/vmware-config2/vmmon-only/./include/driver-config.h:35:0,
from /tmp/vmware-config2/vmmon-only/linux/driverLog.c:26:
include/linux/autoconf.h:2622:0: warning: "CONFIG_LOCALVERSION" redefined
./include/generated/autoconf.h:2622:0: note: this is the location of the previous definition
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config2/vmmon-only/./include/driver-config.h:35:0,
from /tmp/vmware-config2/vmmon-only/linux/driver.c:20:
include/linux/autoconf.h:2622:0: warning: "CONFIG_LOCALVERSION" redefined
./include/generated/autoconf.h:2622:0: note: this is the location of the previous definition
In file included from /tmp/vmware-config2/vmmon-only/./common/vmx86.h:32:0,
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/x86msr.h:164:0: warning: "MSR_THERM2_CTL" redefined
/usr/src/linux-2.6.37.6-0.7/arch/x86/include/asm/msr-index.h:240:0: note: this is the location of the previous definition
/tmp/vmware-config2/vmmon-only/linux/driver.c: In function ‘init_module’:
/tmp/vmware-config2/vmmon-only/linux/driver.c:426:15: error: ‘struct file_operations’ has no member named ‘ioctl’
make[2]: *** [/tmp/vmware-config2/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config2/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.37.6-0.7'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config2/vmmon-only'
Unable to build the vmmon module.
For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and
"http://www.vmware.com/go/unsup-linux-tools".
Execution aborted.
------------------
Can you help me?
Thanks
Don't know.. vmware is always
Submitted by admin on
Don't know.. vmware is always fun :)Do you have all of the source needed? this error makes me thinking about that:WARNING: Symbol version dump /usr/src/linux-2.6.37.6-0.7/Module.symversis missing; modules will have no dependencies and modversions.
Add new comment