You are not logged in.

#1 2013-09-13 14:48:13

Reynaldo_Jose
Member
Registered: 2013-09-02
Posts: 11

[SOLVED] Vmware Workstation 10

DKMS make.log for vmware-modules-9 for kernel 3.10.10-1-ARCH (x86_64)
Fri Sep 13 10:40:15 EDT 2013
vmware-modconfig --console --build-mod -k 3.10.10-1-ARCH vmmon /sbin/gcc /usr/src/linux-3.10.10-1-ARCH/include vmware/
Using 2.6.x kernel build system.
make[1]: Entering directory `/tmp/modconfig-hA6Q9l/vmmon-only'
/sbin/make -C /usr/src/linux-3.10.10-1-ARCH/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[2]: Entering directory `/usr/src/linux-3.10.10-1-ARCH'
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/common/cpuid.o
/tmp/modconfig-hA6Q9l/vmmon-only/linux/driver.c:1342:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-hA6Q9l/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/modconfig-hA6Q9l/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-hA6Q9l/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-hA6Q9l/vmmon-only/vmmon.ko
make[2]: Leaving directory `/usr/src/linux-3.10.10-1-ARCH'
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[2]: Entering directory `/tmp/modconfig-hA6Q9l/vmmon-only'
make[2]: `postbuild' is up to date.
make[2]: Leaving directory `/tmp/modconfig-hA6Q9l/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make[1]: Leaving directory `/tmp/modconfig-hA6Q9l/vmmon-only'
cp -f /lib/modules/3.10.10-1-ARCH/vmware/vmmon.ko .
vmware-modconfig --console --build-mod -k 3.10.10-1-ARCH vmnet /sbin/gcc /usr/src/linux-3.10.10-1-ARCH/include vmware/
Using 2.6.x kernel build system.
make[1]: Entering directory `/tmp/modconfig-jJ2HfW/vmnet-only'
/sbin/make -C /usr/src/linux-3.10.10-1-ARCH/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[2]: Entering directory `/usr/src/linux-3.10.10-1-ARCH'
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/netif.o
/tmp/modconfig-jJ2HfW/vmnet-only/hub.c: In function ‘VNetHubFindHubByID’:
/tmp/modconfig-jJ2HfW/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-jJ2HfW/vmnet-only/hub.c: In function ‘VNetHubAlloc’:
/tmp/modconfig-jJ2HfW/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-jJ2HfW/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/filter.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/vnetEvent.o
  CC [M]  /tmp/modconfig-jJ2HfW/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/modconfig-jJ2HfW/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-jJ2HfW/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-jJ2HfW/vmnet-only/vmnet.ko
make[2]: Leaving directory `/usr/src/linux-3.10.10-1-ARCH'
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[2]: Entering directory `/tmp/modconfig-jJ2HfW/vmnet-only'
make[2]: `postbuild' is up to date.
make[2]: Leaving directory `/tmp/modconfig-jJ2HfW/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make[1]: Leaving directory `/tmp/modconfig-jJ2HfW/vmnet-only'
cp -f /lib/modules/3.10.10-1-ARCH/vmware/vmnet.ko .
vmware-modconfig --console --build-mod -k 3.10.10-1-ARCH vmblock /sbin/gcc /usr/src/linux-3.10.10-1-ARCH/include vmware/
Using 2.6.x kernel build system.
make[1]: Entering directory `/tmp/modconfig-36XYWi/vmblock-only'
/sbin/make -C /usr/src/linux-3.10.10-1-ARCH/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[2]: Entering directory `/usr/src/linux-3.10.10-1-ARCH'
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/dentry.o
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/stubs.o
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/file.o
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/block.o
/tmp/modconfig-36XYWi/vmblock-only/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default]
    .d_revalidate = DentryOpRevalidate,
    ^
/tmp/modconfig-36XYWi/vmblock-only/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default]
/tmp/modconfig-36XYWi/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/modconfig-36XYWi/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast [enabled by default]
       return actualDentry->d_op->d_revalidate(actualDentry, nd);
       ^
/tmp/modconfig-36XYWi/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/inode.o
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/super.o
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/module.o
  CC [M]  /tmp/modconfig-36XYWi/vmblock-only/linux/control.o
/tmp/modconfig-36XYWi/vmblock-only/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default]
    .lookup = InodeOpLookup,
    ^
/tmp/modconfig-36XYWi/vmblock-only/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default]
/tmp/modconfig-36XYWi/vmblock-only/linux/control.c: In function ‘SetupProcDevice’:
/tmp/modconfig-36XYWi/vmblock-only/linux/control.c:211:4: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration]
    controlProcEntry = create_proc_entry(VMBLOCK_CONTROL_DEVNAME,
    ^
/tmp/modconfig-36XYWi/vmblock-only/linux/control.c:211:21: warning: assignment makes pointer from integer without a cast [enabled by default]
    controlProcEntry = create_proc_entry(VMBLOCK_CONTROL_DEVNAME,
                     ^
/tmp/modconfig-36XYWi/vmblock-only/linux/control.c:221:20: error: dereferencing pointer to incomplete type
    controlProcEntry->proc_fops = &ControlFileOps;
                    ^
/tmp/modconfig-36XYWi/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:
/tmp/modconfig-36XYWi/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
    name = getname(buf);
         ^
/tmp/modconfig-36XYWi/vmblock-only/linux/control.c:296:4: warning: passing argument 1 of ‘putname’ from incompatible pointer type [enabled by default]
    putname(name);
    ^
In file included from include/linux/proc_fs.h:8:0,
                 from /tmp/modconfig-36XYWi/vmblock-only/linux/control.c:28:
include/linux/fs.h:2042:13: note: expected ‘struct filename *’ but argument is of type ‘char *’
 extern void putname(struct filename *name);
             ^
cc1: some warnings being treated as errors
make[3]: *** [/tmp/modconfig-36XYWi/vmblock-only/linux/control.o] Error 1
make[2]: *** [_module_/tmp/modconfig-36XYWi/vmblock-only] Error 2
make[2]: Leaving directory `/usr/src/linux-3.10.10-1-ARCH'
make[1]: *** [vmblock.ko] Error 2
make[1]: Leaving directory `/tmp/modconfig-36XYWi/vmblock-only'
make: *** [vmblock.ko] Error 1

thats error log, 2 out of 5 modules wont compile,
Virtual machine communication interface                            failed
VM communication interface socket family                           failed

i've been doing everything from https://wiki.archlinux.org/index.php/VMware
and i have problem there with

dkms -m vmware-modules -v 9 -k $(uname -r) build

applied this patch, still no luck
https://aur.archlinux.org/packages/vmwa … mments=all

Last edited by Reynaldo_Jose (2013-09-13 15:34:24)

Offline

#2 2013-09-13 15:06:54

BxS
Member
From: Portugal
Registered: 2009-04-05
Posts: 24

Re: [SOLVED] Vmware Workstation 10

Take a look at:
hxxps://bbs.archlinux.org/viewtopic.php?id=169472

it may help.

Offline

#3 2013-09-13 15:32:44

Reynaldo_Jose
Member
Registered: 2013-09-02
Posts: 11

Re: [SOLVED] Vmware Workstation 10

haagch wrote:

Ok, my previous answer was useless. So I tracked it a bit. I don't understand it but in /etc/init.d/vmware the function vmwareRealModName seems to do funky things. it uses modprobe -R to "resolve" a module name from an alias and the alias is defined as some pci path. It returns an "vmw_vmci[newline]vmci" in vmci's case and when it calls modprobe to load them both, well, it doesn't work.

(This is what it exactly does:)

$ /sbin/modprobe -R 'pci:v000015ADd00000740sv*sd*bc*sc*i*'
vmw_vmci
vmci

A workaround is that in vmwareStartVmci() you change vmwareLoadModule "$mod" to vmwareLoadModule "$vmci" and in vmwareStartVsock() vmwareLoadModule "$mod" to vmwareLoadModule "$vsock" and the same for vmwareStopVsock() and vmwareStopVmci().

this was the solution, thanks alot BxS, gonna mark as solved.

Offline

Board footer

Powered by FluxBB