VMware Communities
PunchinPreacher
Contributor
Contributor

Vmware Workstation 7.1.4 with Kernel 2.6.39

Having trouble compiling vmware 7.1.4 /w k 2.6.39


Apr 20 18:50:50.461: app-139722951354144| Trying to find a suitable PBM set for kernel 2.6.39-rc3.
Apr 20 18:50:50.462: app-139722951354144| Building module vmmon.
Apr 20 18:50:50.462: app-139722951354144| Extracting the sources of the vmmon module.
Apr 20 18:50:50.472: app-139722951354144| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.39-rc3/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.5.2
Apr 20 18:50:51.315: app-139722951354144| Failed to compile module vmmon!

Reply
0 Kudos
22 Replies
MauroBonder
VMware Employee
VMware Employee

Welcome to the Communities,

Check this link, might be useful http://blog.gnu-designs.com/solved-building-vmware-workstation-modules-on-linux-2-6-32

Good luck

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
Reply
0 Kudos
zarbula
Contributor
Contributor

I think the bigger issue with 2.6.39 is the removal of smp_lock.  When I compiled it I have to fix my Nvidia driver.  Now I'm seeing the same sort of issue with VMware Smiley Sad

here is my error while compiling:

Stopping VMware services:
   VMware USB Arbitrator                                               done
   VM communication interface socket family                            done
   Virtual machine communication interface                             done
   Virtual machine monitor                                             done
   Blocking file system                                                done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/2.6.39-rc3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.39-rc3'
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
/tmp/vmware-root/modules/vmmon-only/linux/driver.c:40: fatal error: linux/smp_lock.h: No such file or directory
compilation terminated.
make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.39-rc3'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Unable to install vmm

I remember that for the Nvidia issue it was something like "perl -pi -e 's/.*smp_lock.h.*\n//'" to fix.  Think it will take something like this to make this work for 2.6.39?

Reply
0 Kudos
martyfelker
Enthusiast
Enthusiast

Could you please correct the link?  If getting 404 or nothing at all.  I am somewhat interested in kernel 2.6.39 which is the default kernel for Fedora Rawhide.

Thanks

Marty

Marty Felker
Reply
0 Kudos
leigh123linux
Contributor
Contributor

Here's the patch it has two bad hunks on vmblock when applying, I edited vmblock by hand.

http://www.fedoraforum.org/leigh123linux/vm/vmware2.6.39.patch

Here's the patched source

http://www.fedoraforum.org/leigh123linux/vm/source.tar.lzma

$ uname -a

Linux main_pc.leigh123linux 2.6.39-0.rc6.git0.0.el6.x86_64 #1 SMP Wed May 4 19:44:16 BST 2011 x86_64 x86_64 x86_64 GNU/Linux

$

Reply
0 Kudos
rgadsdon
Enthusiast
Enthusiast

The patch appeared to work, but produced an OOPS when starting VMware:

-------------

Starting VMware services:
VMware USB Arbitrator                                          [  OK  ]
Virtual machine monitor                                          [  OK  ]
Virtual machine communication interface                 [  OK  ]
VM communication interface socket family              [  OK  ]
Blocking file system
Message from syslogd@rglinux at May  5 12:34:06 …
kernel:Oops: 0010 [#1] SMP

Message from syslogd@rglinux at May  5 12:34:06 …
kernel:last sysfs file: /sys/devices/virtual/misc/vsock/uevent

Message from syslogd@rglinux at May  5 12:34:06 …
kernel:Stack:

Message from syslogd@rglinux at May  5 12:34:06 …
kernel:Call Trace:

Message from syslogd@rglinux at May  5 12:34:06 …
kernel:Code:  Bad RIP value.

Message from syslogd@rglinux at May  5 12:34:06 …
kernel:CR2: 0000000000000000
[FAILED]
Virtual ethernet                                        [  OK  ]

-------------------

Despite this, VMware workstation started OK, but when I attempted to atttach a USB device (SatMap) to the VM (Win7SP1) caused my system (Fedora 14 - Kernel 2.6.39-rc6-git2 X86_64) to hang completely, and a cold boot was needed to fix it..

Robert Gadsdon.

Reply
0 Kudos
xgonzalo
Contributor
Contributor

Same here:

Built vsock module
Starting VMware services:
   VMware USB Arbitrator                                               done
   Virtual machine monitor                                             done
   Virtual machine communication interface                             done
   VM communication interface socket family                            done
   Blocking file system
Message from syslogd@glaptop at May 20 18:47:37 ...
kernel:[ 5697.577474] Oops: 0010 [#1] SMP
Message from syslogd@glaptop at May 20 18:47:37 ...
kernel:[ 5697.577479] last sysfs file: /sys/devices/virtual/misc/vsock/uevent
Message from syslogd@glaptop at May 20 18:47:37 ...
kernel:[ 5697.577662] Stack:
Message from syslogd@glaptop at May 20 18:47:37 ...
kernel:[ 5697.577682] Call Trace:
Message from syslogd@glaptop at May 20 18:47:37 ...
kernel:[ 5697.577744] Code:  Bad RIP value.
Message from syslogd@glaptop at May 20 18:47:37 ...
kernel:[ 5697.577757] CR2: 0000000000000000
                                                                      failed
   Virtual ethernet                                                    done
Unable to start services
Reply
0 Kudos
PDMC
Contributor
Contributor

I've been unable to get 7.1.4 to work with the openSuse 11.4 Tumbleweed version since upgrading to kernel 2.6.39-30, the current kernel release for Tumbleweed, using these or any other patch scripts I've found by search.

???

Reply
0 Kudos
rgadsdon
Enthusiast
Enthusiast

There is a new, improved patch now available:

http://weltall.heliohost.org/wordpress/2011/05/14/running-vmware-workstation-player-on-linux-2-6-39-...

- and it compiles and installes OK, and works (kernel 2.6.39 - from kernel.org)..

(FYI, the site is sometimes 404, for some reason..  just try a bit later..)

Robert Gadsdon.

Reply
0 Kudos
PDMC
Contributor
Contributor

Thanks Bob but I'm a bit to dense to see exactly how to apply the patch.

Lookiing at the script it looks like you have to untar each of the tarbals in the vmware modules install directory to a directory named source-original run the script from the directory up one level from source-original and source then tar them back up and move them back to the modules/source directory?

Reply
0 Kudos
martyfelker
Enthusiast
Enthusiast

Got this while trying to  run vmware after applying your patch.

Host  = openSUSE Factory  kernel 2.6.39-2-vanilla

Any ideas??

Thanks

Marty Felker

---------------------------------------------------------------------------------------

/usr/bin> ./vmware
Logging to /tmp/vmware-marty/setup-5852.log
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmmon.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Monitor.
author:         VMware, Inc.
srcversion:     DFE9035F8F3EC713B7EC543
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmnet.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Networking Driver.
author:         VMware, Inc.
srcversion:     F08F0A4F6CD990A288AD26D
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmmon.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Monitor.
author:         VMware, Inc.
srcversion:     DFE9035F8F3EC713B7EC543
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmnet.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Networking Driver.
author:         VMware, Inc.
srcversion:     F08F0A4F6CD990A288AD26D
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmmon.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Monitor.
author:         VMware, Inc.
srcversion:     DFE9035F8F3EC713B7EC543
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmnet.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Networking Driver.
author:         VMware, Inc.
srcversion:     F08F0A4F6CD990A288AD26D
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmmon.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Monitor.
author:         VMware, Inc.
srcversion:     DFE9035F8F3EC713B7EC543
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmnet.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Networking Driver.
author:         VMware, Inc.
srcversion:     F08F0A4F6CD990A288AD26D
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmmon.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Monitor.
author:         VMware, Inc.
srcversion:     DFE9035F8F3EC713B7EC543
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
filename:       /lib/modules/2.6.39-2-vanilla/misc/vmnet.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Networking Driver.
author:         VMware, Inc.
srcversion:     F08F0A4F6CD990A288AD26D
depends:       
vermagic:       2.6.39-2-vanilla SMP mod_unload modversions
ERROR: modinfo: could not find module vmblock
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock

Marty Felker
Reply
0 Kudos
rgadsdon
Enthusiast
Enthusiast

It is not _my_ patch, I was just providing a link to the authors' site.   If you go there, you will see there is a Q and A thread on application etc....

Apologies for any confusion...

Robert Gadsdon.

Reply
0 Kudos
martyfelker
Enthusiast
Enthusiast

No problem.  I was on that site and the author did have 2 patrches for 2.6.39 (one of them 'fixed').  I will contact him directly with any more questions.  It would be interesting though if anybody else has had success with this.  The author says it works on a kernel compiled directly from kernel.org.  openSUSE VAnialla kerenels use the same sources and are not modified for SUSE.  Eventually VMwar ewill get  around to a fix because they must.  I still have a working versiobn of VMware on Fedora Rawhide with the 2.6.38 kernel.

Marty

Marty Felker
Reply
0 Kudos
PDMC
Contributor
Contributor

I got the fixed patch to work.

See this thread, post by audiocomp then the suggested < posted by malcolmlewis.

http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/460324-kernel-upgrade-2-6-39-3...

Reply
0 Kudos
martyfelker
Enthusiast
Enthusiast

Yes. Patch worked here as well - openSUSE Factory x64 kernel=2.6.39-2-desktop.

Kudos to all and especially  the developer of course.

Marty

Marty Felker
Reply
0 Kudos
matthewls
Enthusiast
Enthusiast

Patch works and now 7.14 is running under Ubuntu 10.10 kernel 2.6.39.

Thanks to all!

Reply
0 Kudos
martyfelker
Enthusiast
Enthusiast

I've install kernel 3.0.0-rc1-next-20110603-0.0.6.d59a25a-vanilla on openSUSE 12.1 Milestone 1 and it actually boots(pretty kool disaply manager in facdt).  Would you like to take a crack at patching kernel 3.0 (used to be called 2.6.40!)

Marty

Marty Felker
Reply
0 Kudos
forumi0721hotma
Contributor
Contributor

It is not suitable for me...

I have only pvscsi.tar vmblock.tar vmci.tar vmhgfs.tar vmmemctl.tar vmsync.tar vmwgfx.tar vmxnet.tar vmxnet3.tar vsock.tar in vmware-tools-distrib/lib/modules/source...

I want to install vmware tools. please help me.

compile error log

Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/usr/bin/gcc-4.4".
The path "/usr/bin/gcc-4.4" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers of the running kernel at
"/lib/modules/2.6.39-1-686-pae/build/include".
The path "/lib/modules/2.6.39-1-686-pae/build/include" appears to be a valid
path to the kernel headers of the running kernel.
Would you like to change it? [no]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make -C /lib/modules/2.6.39-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.39-1-686-pae'
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/backdoor.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/backdoorGcc32.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/bdhandler.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpName.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpNameLinux.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpNameLite.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/dentry.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/dir.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/file.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/filesystem.o
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c:48:28: error: linux/smp_lock.h: 그런 파일이나 디렉터리가 없습니다
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c:72: error: ‘SPIN_LOCK_UNLOCKED’ undeclared here (not in a function)
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c:137: error: unknown field ‘get_sb’ specified in initializer
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c:137: warning: initialization from incompatible pointer type
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c: In function ‘HgfsGetSb’:
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c:493: error: implicit declaration of function ‘get_sb_nodev’
make[4]: *** [/tmp/vmware-root/modules/vmhgfs-only/filesystem.o] 오류 1
make[3]: *** [_module_/tmp/vmware-root/modules/vmhgfs-only] 오류 2
make[2]: *** [sub-make] 오류 2
make[1]: *** [all] 오류 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.39-1-686-pae'
make: *** [vmhgfs.ko] 오류 2
make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.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 Enter key to continue ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make -C /lib/modules/2.6.39-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.39-1-686-pae'
  CC [M]  /tmp/vmware-root/modules/vmxnet-only/vmxnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmxnet-only/vmxnet.mod.o
  LD [M]  /tmp/vmware-root/modules/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.39-1-686-pae'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make[1]: `postbuild'는 이미 갱신되었습니다.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/2.6.39-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.39-1-686-pae'
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
/tmp/vmware-root/modules/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/vmware-root/modules/vmblock-only/linux/dentry.c:107: error: implicit declaration of function ‘path_lookup’
make[4]: *** [/tmp/vmware-root/modules/vmblock-only/linux/dentry.o] 오류 1
make[3]: *** [_module_/tmp/vmware-root/modules/vmblock-only] 오류 2
make[2]: *** [sub-make] 오류 2
make[1]: *** [all] 오류 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.39-1-686-pae'
make: *** [vmblock.ko] 오류 2
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
The vmblock module enables dragging or copying files from within a host and
dropping or pasting them onto your guest (host to guest drag and drop and file
copy/paste).  The rest of the software provided by VMware Tools is designed to
work independently of this feature (including guest to host drag and drop and
file copy/paste).
If you would like the host to guest drag and drop and file copy/paste features,
you can install the driver by running vmware-config-tools.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 Enter key to continue ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/2.6.39-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.39-1-686-pae'
  CC [M]  /tmp/vmware-root/modules/vmci-only/kernelStubsLinux.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciDatagram.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciEvent.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciGuestDs.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciGuestKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciProcess.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciQueuePair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciUtil.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmci_drv.o
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:32:28: error: linux/smp_lock.h: 그런 파일이나 디렉터리가 없습니다
/tmp/vmware-root/modules/vmci-only/vmci_drv.c: In function ‘vmci_unlocked_ioctl’:
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:718: error: implicit declaration of function ‘lock_kernel’
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:720: error: implicit declaration of function ‘unlock_kernel’
make[4]: *** [/tmp/vmware-root/modules/vmci-only/vmci_drv.o] 오류 1
make[3]: *** [_module_/tmp/vmware-root/modules/vmci-only] 오류 2
make[2]: *** [sub-make] 오류 2
make[1]: *** [all] 오류 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.39-1-686-pae'
make: *** [vmci.ko] 오류 2
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
The communication service is used in addition to the standard communication
between the guest and the host.  The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the VMCI feature, you can install the driver by running
vmware-config-tools.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 Enter key to continue ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/2.6.39-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.39-1-686-pae'
  CC [M]  /tmp/vmware-root/modules/vmci-only/kernelStubsLinux.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciDatagram.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciEvent.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciGuestDs.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciGuestKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciProcess.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciQueuePair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmciUtil.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/vmci_drv.o
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:32:28: error: linux/smp_lock.h: 그런 파일이나 디렉터리가 없습니다
/tmp/vmware-root/modules/vmci-only/vmci_drv.c: In function ‘vmci_unlocked_ioctl’:
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:718: error: implicit declaration of function ‘lock_kernel’
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:720: error: implicit declaration of function ‘unlock_kernel’
make[4]: *** [/tmp/vmware-root/modules/vmci-only/vmci_drv.o] 오류 1
make[3]: *** [_module_/tmp/vmware-root/modules/vmci-only] 오류 2
make[2]: *** [sub-make] 오류 2
make[1]: *** [all] 오류 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.39-1-686-pae'
make: *** [vmci.ko] 오류 2
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
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 Tools 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-tools.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.]
The module vmxnet3 has already been installed on this system by another
installer or package and will not be modified by this installer.  Use the flag
--clobber-kernel-modules=vmxnet3 to override.
The module pvscsi has already been installed on this system by another
installer or package and will not be modified by this installer.  Use the flag
--clobber-kernel-modules=pvscsi to override.
Unable to create symlink "/etc/cups/ppd/VMware_Virtual_Printer.ppd" pointing to
file "/usr/lib/vmware-tools/configurator/thinprint.ppd".
Execution aborted.
Reply
0 Kudos
djpalindrome
Enthusiast
Enthusiast

I'm in the same boat (I think) as forumi0721hotmail; I have a Windows 7 SP1 x64 host running a Debian Sid guest.

The last kernel on which VMware Tools compiled (almost) successfully was 2.6.38.

All of these patch scripts addressed to Linux hosts are ill-suited to the (I'm guessing) vast majority of users who are virtualizing Linux, not Windows.

Reply
0 Kudos