You are not logged in.

Pages: 1

#1 2013-09-21 13:58:25

Syrius00
Member
From: Perugia, Italy
Registered: 2012-10-01
Posts: 16

[SOLVED] VMWare Player: unable to start modules

Hi guys

I hope I'm posting this in the right section.

I'm trying to install VMWare Player on my machine. I have the latest kernel installed (3.11.1-1) and I have followed the instructions on the wiki page. Precisely I did:

- Install the latest VMPlayer (6)

- Run vmware-patch

- Run vmware-modconfig --console --install-all

In this last step, it seems like compiling goes well, but it is unable to start core modules. Here's the output:

[archsyrius@archspire Downloads]$ sudo vmware-modconfig --console --install-all
Stopping VMware services:
   VMware Authentication Daemon                                        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/modconfig-q4Yy9W/vmmon-only'
/sbin/make -C /lib/modules/3.11.1-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.11.1-1-ARCH'
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/common/cpuid.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmmon-only/vmcore/moduleloop.o
/tmp/modconfig-q4Yy9W/vmmon-only/linux/driver.c:1342:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
  LD [M]  /tmp/modconfig-q4Yy9W/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-q4Yy9W/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-q4Yy9W/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-3.11.1-1-ARCH'
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-q4Yy9W/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-q4Yy9W/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-q4Yy9W/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-q4Yy9W/vmnet-only'
/sbin/make -C /lib/modules/3.11.1-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.11.1-1-ARCH'
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/filter.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/smac_compat.o
/tmp/modconfig-q4Yy9W/vmnet-only/hub.c: In function ‘VNetHubFindHubByID’:
/tmp/modconfig-q4Yy9W/vmnet-only/hub.c:132:49: warning: argument to ‘sizeof’ in ‘memcmp’ call is the same expression as the first source; did you mean to provide an explicit length? [-Wsizeof-pointer-memaccess]
         memcmp(idNum, currHub->id.pvnID, sizeof idNum))) {
                                                 ^
/tmp/modconfig-q4Yy9W/vmnet-only/hub.c: In function ‘VNetHubAlloc’:
/tmp/modconfig-q4Yy9W/vmnet-only/hub.c:315:36: warning: argument to ‘sizeof’ in ‘memcpy’ call is the same pointer type ‘uint8 *’ as the destination; expected ‘uint8’ or an explicit length [-Wsizeof-pointer-memaccess]
   memcpy(hub->id.pvnID, id, sizeof id);
                                    ^
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/vnetEvent.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/modconfig-q4Yy9W/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-q4Yy9W/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-q4Yy9W/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-3.11.1-1-ARCH'
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-q4Yy9W/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-q4Yy9W/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-q4Yy9W/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-q4Yy9W/vmci-only'
/sbin/make -C /lib/modules/3.11.1-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.11.1-1-ARCH'
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciResource.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-q4Yy9W/vmci-only/driverLog.o
  LD [M]  /tmp/modconfig-q4Yy9W/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-q4Yy9W/vmci-only/vmci.mod.o
  LD [M]  /tmp/modconfig-q4Yy9W/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.11.1-1-ARCH'
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-q4Yy9W/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-q4Yy9W/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-q4Yy9W/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-q4Yy9W/vsock-only'
/sbin/make -C /lib/modules/3.11.1-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.11.1-1-ARCH'
  CC [M]  /tmp/modconfig-q4Yy9W/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/modconfig-q4Yy9W/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/modconfig-q4Yy9W/vsock-only/linux/notifyQState.o
  CC [M]  /tmp/modconfig-q4Yy9W/vsock-only/linux/util.o
  CC [M]  /tmp/modconfig-q4Yy9W/vsock-only/linux/stats.o
  CC [M]  /tmp/modconfig-q4Yy9W/vsock-only/linux/notify.o
  CC [M]  /tmp/modconfig-q4Yy9W/vsock-only/driverLog.o
  LD [M]  /tmp/modconfig-q4Yy9W/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-q4Yy9W/vsock-only/vsock.mod.o
  LD [M]  /tmp/modconfig-q4Yy9W/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-3.11.1-1-ARCH'
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-q4Yy9W/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-q4Yy9W/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-q4Yy9W/vsock-only'
Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                            failed
   VM communication interface socket family                           failed
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done
Unable to start services

Any suggestions? Thank you all in advance.

Last edited by Syrius00 (2013-09-28 11:13:10)

Offline

#2 2013-09-23 09:19:17

chsinpc
Member
From: Munich, Germany
Registered: 2013-04-07
Posts: 4

Re: [SOLVED] VMWare Player: unable to start modules

Hi Syrius00,

The solution can be found in https://bbs.archlinux.org/viewtopic.php?id=169472
See the post of haagch (Thanks a lot for investigating this !)

Offline

#3 2013-09-24 23:41:03

Syrius00
Member
From: Perugia, Italy
Registered: 2012-10-01
Posts: 16

Re: [SOLVED] VMWare Player: unable to start modules

Thank you chsinpc. I solved my problem and because of this I am very grateful to you smile

Offline

Pages: 1

Board footer

Powered by FluxBB