VMware Workstation 7 vmnet problem

koecko · #1 19th March 2010, 02:13 PM

Hi @ all,

I'm new to the formum and since Dez. to Fedora, without any problems up to now

I'm running Fed 12 - 64bit and do have VMware Worksation 7 installed. Since the last kernel update on monday I'm not able to load the workstation anymore, I do get vmnet errors. I have allready googed but I didn't find the answer.

Does anyone has an idea how to get it running again?
Many thanks for any hints and your support in advance!

reg
Koecko

PS: Below I have attached the VMware log:

Mar 19 14:05:05.807: app-140283904009984| Log for VMware Workstation pid=3560 version=7.0.0 build=build-203739 option=Release
Mar 19 14:05:05.807: app-140283904009984| The process is 64-bit.
Mar 19 14:05:05.807: app-140283904009984| Host codepage=UTF-8 encoding=UTF-8
Mar 19 14:05:05.807: app-140283904009984| Logging to /tmp/vmware-root/setup-3560.log
Mar 19 14:05:05.902: app-140283904009984| modconf query interface initialized
Mar 19 14:05:05.903: app-140283904009984| modconf library initialized
Mar 19 14:05:05.932: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:05.937: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:05.945: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:05.956: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:05.964: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:06.001: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.003: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.005: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.007: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.009: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.031: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.033: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.035: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.038: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.040: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.044: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:06.053: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:06.089: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.091: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.093: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.095: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.097: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.101: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:06.109: app-140283904009984| Your GCC version: 4.4
Mar 19 14:05:06.160: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.162: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.164: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.166: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.168: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.492: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:06.492: app-140283904009984| Building module vmmon.
Mar 19 14:05:06.502: app-140283904009984| Extracting the sources of the vmmon module.
Mar 19 14:05:06.571: app-140283904009984| 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.32.9-70.fc12.x86_64/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.4.3
Mar 19 14:05:13.528: app-140283904009984| Installing module vmmon from /tmp/vmware-root/modules/vmmon.o.
Mar 19 14:05:13.548: app-140283904009984| Registering file: /usr/lib/vmware-installer/1.1/vmware-installer --register-file vmware-player-app regular /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.o
Mar 19 14:05:15.387: app-140283904009984| Registering file: /usr/lib/vmware-installer/1.1/vmware-installer --register-file vmware-player-app regular /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.ko
Mar 19 14:05:22.544: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:22.545: app-140283904009984| Building module vmnet.
Mar 19 14:05:22.545: app-140283904009984| Extracting the sources of the vmnet module.
Mar 19 14:05:22.576: app-140283904009984| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmnet-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.32.9-70.fc12.x86_64/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.4.3
Mar 19 14:05:28.289: app-140283904009984| Failed to compile module vmnet!
Mar 19 14:05:28.293: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:28.293: app-140283904009984| Building module vmblock.
Mar 19 14:05:28.294: app-140283904009984| Extracting the sources of the vmblock module.
Mar 19 14:05:28.336: app-140283904009984| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmblock-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.32.9-70.fc12.x86_64/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.4.3
Mar 19 14:05:32.058: app-140283904009984| Installing module vmblock from /tmp/vmware-root/modules/vmblock.o.
Mar 19 14:05:32.061: app-140283904009984| Registering file: /usr/lib/vmware-installer/1.1/vmware-installer --register-file vmware-player-app regular /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmblock.o
Mar 19 14:05:32.509: app-140283904009984| Registering file: /usr/lib/vmware-installer/1.1/vmware-installer --register-file vmware-player-app regular /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmblock.ko
Mar 19 14:05:33.443: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:33.444: app-140283904009984| Building module vmci.
Mar 19 14:05:33.444: app-140283904009984| Extracting the sources of the vmci module.
Mar 19 14:05:33.474: app-140283904009984| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmci-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.32.9-70.fc12.x86_64/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.4.3
Mar 19 14:05:34.635: app-140283904009984| Failed to compile module vmci!
Mar 19 14:05:34.639: app-140283904009984| Trying to find a suitable PBM set for kernel 2.6.32.9-70.fc12.x86_64.
Mar 19 14:05:34.640: app-140283904009984| Building module vmci.
Mar 19 14:05:34.640: app-140283904009984| Extracting the sources of the vmci module.
Mar 20 14:05:34.650: app-140283904009984| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmci-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.32.9-70.fc12.x86_64/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.4.3
Mar 19 14:05:35.430: app-140283904009984| Failed to compile module vmci!

Milena · #2 19th March 2010, 03:55 PM

Hi & Welcome.

Do you have the kernel-devel and kernel-headers packages installed for the 2.6.32.9-70 kernel ?
I have no problems with Workstation 7.0.1 build-227600, it builds a new module after kernel updates and starts up normal:

Code:

bash-4.0$ vmware
Logging to /tmp/vmware-M/setup-15199.log
filename:       /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Monitor.
author:         VMware, Inc.
srcversion:     1BBFFDFF731D21908BB9AF6
depends:        
vermagic:       2.6.32.9-70.fc12.x86_64 SMP mod_unload 
filename:       /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmnet.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Networking Driver.
author:         VMware, Inc.
srcversion:     E52058FD837D53FA2E505E8
depends:        
vermagic:       2.6.32.9-70.fc12.x86_64 SMP mod_unload 
filename:       /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmblock.ko
supported:      external
version:        1.1.2.0
license:        GPL v2
description:    VMware Blocking File System
author:         VMware, Inc.
srcversion:     400149ED038D22A87322D56
depends:        
vermagic:       2.6.32.9-70.fc12.x86_64 SMP mod_unload 
parm:           root:The directory the file system redirects to. (charp)
filename:       /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmci.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Communication Interface (VMCI).
author:         VMware, Inc.
srcversion:     10CF7904714E1EDA4361B9F
depends:        
vermagic:       2.6.32.9-70.fc12.x86_64 SMP mod_unload 
filename:       /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vsock.ko
supported:      external
license:        GPL v2
version:        1.0.0.0
description:    VMware Virtual Socket Family
author:         VMware, Inc.
srcversion:     BC1943DCE52AE461DCC2D43
depends:        vmci
vermagic:       2.6.32.9-70.fc12.x86_64 SMP mod_unload 
filename:       /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.ko
supported:      external
license:        GPL v2
description:    VMware Virtual Machine Monitor.
author:         VMware, Inc.
srcversion:     1BBFFDFF731D21908BB9AF6
depends:        
vermagic:       2.6.32.9-70.fc12.x86_64 SMP mod_unload

koecko · #3 23rd March 2010, 10:56 AM

Hi,

thanks for your reply.
In the past I didn't had any problems too, the problem appeared after the last kernel update,
from my point of view it is a vmnet problem

There is a new VMW Workstation Beta now, but I'm not able to upgrade because the old one is not loaded? Can you pls give me an advise how I can uninstall the VMware workstation?

Thanks!
reg, Dan

Logging to /tmp/vmware-dan/setup-7902.log
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 9FB063A3FC33465439B2834
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
ERROR: modinfo: could not find module vmnet
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmblock.ko
supported: external
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 400149ED038D22A87322D56
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
parm: root:The directory the file system redirects to. (charp)
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 9FB063A3FC33465439B2834
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
ERROR: modinfo: could not find module vmnet
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmblock.ko
supported: external
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 400149ED038D22A87322D56
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
parm: root:The directory the file system redirects to. (charp)
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 9FB063A3FC33465439B2834
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
ERROR: modinfo: could not find module vmnet
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmblock.ko
supported: external
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 400149ED038D22A87322D56
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
parm: root:The directory the file system redirects to. (charp)
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 9FB063A3FC33465439B2834
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
ERROR: modinfo: could not find module vmnet
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmblock.ko
supported: external
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 400149ED038D22A87322D56
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
parm: root:The directory the file system redirects to. (charp)
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 9FB063A3FC33465439B2834
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
ERROR: modinfo: could not find module vmnet
filename: /lib/modules/2.6.32.9-70.fc12.x86_64/misc/vmblock.ko
supported: external
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 400149ED038D22A87322D56
depends:
vermagic: 2.6.32.9-70.fc12.x86_64 SMP mod_unload
parm: root:The directory the file system redirects to. (charp)
ERROR: modinfo: could not find module vmci
ERROR: modinfo: could not find module vsock
b70553b3c21c3e92dc37a52c858c4c

.................................................. ................

Mortosa · #4 23rd March 2010, 02:50 PM

I use F12 64bit and love it. On my work laptop I run VMWare Workstation as well since there are windows programs I am forced to use. Workstation was running great but I too had the problem with modules after a kernel update. So in doing some digging I found a patch at the vmware communities website. This patch helped me and VMWare is now working again.

http://communities.vmware.com/thread/239221

koecko · #5 24th March 2010, 07:57 PM

Hi,

thanks for the replies @ all.

I have been able to resolve my problem.
I uninstalled kernel-devel and kernel-header,
afterwards installed kernel-devel again, and then I have been able to upgrade my installation to the new workstation 7 beta. Everthing is running again

Thanks,
reg, Dan

veranyon · #6 25th March 2010, 01:19 PM

Quote:

Originally Posted by Mortosa

I use F12 64bit and love it. On my work laptop I run VMWare Workstation as well since there are windows programs I am forced to use. Workstation was running great but I too had the problem with modules after a kernel update. So in doing some digging I found a patch at the vmware communities website. This patch helped me and VMWare is now working again.

http://communities.vmware.com/thread/239221

Code:

./patch-modules.sh 
mkdir: cannot create directory `original': File exists
./patch-modules.sh: line 7: patch: command not found
Stopping VMware services:
   VMware USB Arbitrator                                   [  OK  ]
   VM communication interface socket family                [  OK  ]
   Virtual machine communication interface                 [  OK  ]
   Virtual machine monitor                                 [  OK  ]
   Blocking file system                                    [  OK  ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/2.6.32.9-70.fc12.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32.9-70.fc12.x86_64'
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
In file included from /tmp/vmware-root/modules/vmmon-only/./include/vm_asm.h:42,
                 from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:100:
/tmp/vmware-root/modules/vmmon-only/./include/vm_asm_x86_64.h:50:7: warning: "_MSC_VER" is not defined
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
In file included from /tmp/vmware-root/modules/vmmon-only/./include/vm_asm.h:42,
                 from /tmp/vmware-root/modules/vmmon-only/linux/hostif.c:67:
/tmp/vmware-root/modules/vmmon-only/./include/vm_asm_x86_64.h:50:7: warning: "_MSC_VER" is not defined
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function 'HostIFReadUptimeWork':
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c:1944: warning: 'newUpBase' may be used uninitialized in this function
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
/tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function 'IOMMUUnregisterDeviceInt':
/tmp/vmware-root/modules/vmmon-only/linux/iommu.c:216: warning: ignoring return value of 'device_attach', declared with attribute warn_unused_result
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/task.o
In file included from /tmp/vmware-root/modules/vmmon-only/./include/vm_asm.h:42,
                 from /tmp/vmware-root/modules/vmmon-only/common/task.c:50:
/tmp/vmware-root/modules/vmmon-only/./include/vm_asm_x86_64.h:50:7: warning: "_MSC_VER" is not defined
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
In file included from /tmp/vmware-root/modules/vmmon-only/./include/vm_asm.h:42,
                 from /tmp/vmware-root/modules/vmmon-only/common/vmx86.c:43:
/tmp/vmware-root/modules/vmmon-only/./include/vm_asm_x86_64.h:50:7: warning: "_MSC_VER" is not defined
  CC [M]  /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32.9-70.fc12.x86_64'
make -C $PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/2.6.32.9-70.fc12.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32.9-70.fc12.x86_64'
  CC [M]  /tmp/vmware-root/modules/vmnet-only/driver.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/hub.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/userif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/netif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/filter.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32.9-70.fc12.x86_64'
make -C $PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Built vmnet module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/2.6.32.9-70.fc12.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32.9-70.fc12.x86_64'
  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
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/file.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/inode.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/module.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/super.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32.9-70.fc12.x86_64'
make -C $PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'

veranyon · #7 25th March 2010, 06:03 PM

Code:

make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
Built vmblock module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/2.6.32.9-70.fc12.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32.9-70.fc12.x86_64'
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
In file included from /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:48:
/tmp/vmware-root/modules/vmci-only/./include/pgtbl.h: In function 'PgtblVa2MPN':
/tmp/vmware-root/modules/vmci-only/./include/pgtbl.h:301: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/./include/pgtbl.h: In function 'PgtblVa2Page':
/tmp/vmware-root/modules/vmci-only/./include/pgtbl.h:373: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c: In function 'VMCIHost_SignalCall':
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:328: error: 'TASK_NORMAL' undeclared (first use in this function)
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:328: error: (Each undeclared identifier is reported only once
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:328: error: for each function it appears in.)
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c: In function 'VMCIHost_WaitForCallLocked':
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:370: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:370: error: 'TASK_INTERRUPTIBLE' undeclared (first use in this function)
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:378: error: implicit declaration of function 'schedule'
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:386: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:386: error: 'TASK_RUNNING' undeclared (first use in this function)
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:390: error: implicit declaration of function 'signal_pending'
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c: In function 'VMCI_SignalEvent':
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:682: error: 'TASK_NORMAL' undeclared (first use in this function)
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c: In function 'VMCI_WaitOnEventInterruptible':
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:739: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:739: error: 'TASK_INTERRUPTIBLE' undeclared (first use in this function)
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:751: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:751: error: 'TASK_RUNNING' undeclared (first use in this function)
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c: In function 'VMCIHost_GetUserMemory':
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:1438: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:1440: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:1459: error: dereferencing pointer to incomplete type
/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.c:1487: error: dereferencing pointer to incomplete type
make[2]: *** [/tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o] Error 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmci-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.32.9-70.fc12.x86_64'
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Unable to install vmci

---------- Post added at 08:03 PM CDT ---------- Previous post was at 03:27 PM CDT ----------

Found.
http://wiki.archlinux.org/index.php/Installing_VMware

"VMware and kernel 2.6.32

To patch VMware modules we have to add #include "compat_sched.h" to some files (the tarring is not needed with vmware 7.x.x).

# cd /tmp
# tar xf /usr/lib/vmware/modules/source/vmnet.tar
# nano vmnet-only/vnetUserListener.c (near line 37 add #include "compat_sched.h")
# tar cf /usr/lib/vmware/modules/source/vmnet.tar vmnet-only
# tar xf /usr/lib/vmware/modules/source/vmci.tar
# nano vmci-only/linux/vmciKernelIf.c vmci-only/include/pgtbl.h (add #include "compat_sched.h" around 30 line)
# tar cf /usr/lib/vmware/modules/source/vmci.tar vmci-only
# vmware-modconfig --console --install-all
"

gihad · #8 2nd May 2010, 03:09 AM

Hi all, im just installed VMware-Workstation-7.0.0-203739.i386.bundle. My kernel on FEDORA 12 is 2.6.32.11-99.fc12.i686.PAE, and i'm having exactly the same problem: cannot compile module vmnet.
I tried everything i found on google, patching, adding lines... but after whilees of searching, i've found out that VMWare WS7 should have not problems with kernel 2.6.32. Could that be some problem with kernel PAE?? Anyone can give me a hint?