You are not logged in.

#1 2014-12-04 09:53:26

freaks
Member
Registered: 2010-11-10
Posts: 63

[vmware] Virtual machine communication interface failed

hello,

on a fresh install of archlinux, i have installed vmware workstation 11.0 but when i execute this command :

vmware-modconfig --console --install-all

i have this error

Virtual machine communication interface                            failed

full log

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
make : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
Using kernel build system.
/sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/common/cpuid.o
/tmp/modconfig-sc9HDC/vmmon-only/linux/driver.c:1332:1: attention : always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-sc9HDC/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/modconfig-sc9HDC/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-sc9HDC/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-sc9HDC/vmmon-only/vmmon.ko
make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1] : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
make[1]: « postbuild » est à jour.
make[1] : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
cp -f vmmon.ko ./../vmmon.o
make : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
make : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
Using kernel build system.
/sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/vnetEvent.o
  CC [M]  /tmp/modconfig-sc9HDC/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/modconfig-sc9HDC/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-sc9HDC/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-sc9HDC/vmnet-only/vmnet.ko
make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1] : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
make[1]: « postbuild » est à jour.
make[1] : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
cp -f vmnet.ko ./../vmnet.o
make : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                            failed
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done
Unable to start services
[root@hulk vmware-root]# ls
vmware-818.log		   vmware-authdlauncher-2058.log  vmware-vmis-1888.log
vmware-apploader-1976.log  vmware-vmis-1407.log		  vmware-vmis-1910.log
vmware-apploader-818.log   vmware-vmis-1429.log
[root@hulk vmware-root]# chown gael:users *
[root@hulk vmware-root]# chown -R gael:users ./
[root@hulk vmware-root]# modprobe vmci
modprobe: FATAL: Module vmci not found.
[root@hulk vmware-root]# vmware-modconfig --console --install-all -v
/usr/lib/vmware/bin/vmware-modconfig-console: invalid option -- 'v'
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
make : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
Using kernel build system.
/sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/common/cpuid.o
/tmp/modconfig-KdpHql/vmmon-only/linux/driver.c:1332:1: attention : always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-KdpHql/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/modconfig-KdpHql/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-KdpHql/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-KdpHql/vmmon-only/vmmon.ko
make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1] : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
make[1]: « postbuild » est à jour.
make[1] : on quitte le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
cp -f vmmon.ko ./../vmmon.o
make : on quitte le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
make : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
Using kernel build system.
/sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/vnetEvent.o
  CC [M]  /tmp/modconfig-KdpHql/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/modconfig-KdpHql/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-KdpHql/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-KdpHql/vmnet-only/vmnet.ko
make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1] : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
make[1]: « postbuild » est à jour.
make[1] : on quitte le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
cp -f vmnet.ko ./../vmnet.o
make : on quitte le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                            failed
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done
Unable to start services

thanks for your help

Offline

#2 2015-02-01 16:57:09

dslink
Member
From: USA
Registered: 2012-02-23
Posts: 48

Re: [vmware] Virtual machine communication interface failed

Also having the same problem

dustin ~ $ sudo vmware-modconfig --console --install-all
[sudo] password for dustin: 
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
make: Entering directory '/tmp/modconfig-KZzuso/vmmon-only'
Using kernel build system.
/sbin/make -C /lib/modules/3.18.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.18.4-1-ARCH/build'
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/common/cpuid.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-KZzuso/vmmon-only/vmcore/moduleloop.o
/tmp/modconfig-KZzuso/vmmon-only/linux/driver.c:1332:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
  LD [M]  /tmp/modconfig-KZzuso/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-KZzuso/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-KZzuso/vmmon-only/vmmon.ko
make[1]: Leaving directory '/usr/lib/modules/3.18.4-1-ARCH/build'
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-KZzuso/vmmon-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-KZzuso/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory '/tmp/modconfig-KZzuso/vmmon-only'
make: Entering directory '/tmp/modconfig-KZzuso/vmnet-only'
Using kernel build system.
/sbin/make -C /lib/modules/3.18.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.18.4-1-ARCH/build'
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/vnetEvent.o
In file included from include/linux/pci.h:34:0,
                 from /tmp/modconfig-KZzuso/vmnet-only/compat_netdevice.h:27,
                 from /tmp/modconfig-KZzuso/vmnet-only/netif.c:43:
include/linux/pci_ids.h:2248:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
 #define PCI_VENDOR_ID_VMWARE  0x15ad
 ^
In file included from /tmp/modconfig-KZzuso/vmnet-only/net.h:38:0,
                 from /tmp/modconfig-KZzuso/vmnet-only/vnetInt.h:26,
                 from /tmp/modconfig-KZzuso/vmnet-only/netif.c:42:
/tmp/modconfig-KZzuso/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition
 #define PCI_VENDOR_ID_VMWARE                    0x15AD
 ^
  CC [M]  /tmp/modconfig-KZzuso/vmnet-only/vnetUserListener.o
In file included from /tmp/modconfig-KZzuso/vmnet-only/net.h:38:0,
                 from /tmp/modconfig-KZzuso/vmnet-only/vnetInt.h:26,
                 from /tmp/modconfig-KZzuso/vmnet-only/bridge.c:52:
/tmp/modconfig-KZzuso/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
 #define PCI_VENDOR_ID_VMWARE                    0x15AD
 ^
In file included from include/linux/pci.h:34:0,
                 from /tmp/modconfig-KZzuso/vmnet-only/compat_netdevice.h:27,
                 from /tmp/modconfig-KZzuso/vmnet-only/bridge.c:51:
include/linux/pci_ids.h:2248:0: note: this is the location of the previous definition
 #define PCI_VENDOR_ID_VMWARE  0x15ad
 ^
  LD [M]  /tmp/modconfig-KZzuso/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-KZzuso/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-KZzuso/vmnet-only/vmnet.ko
make[1]: Leaving directory '/usr/lib/modules/3.18.4-1-ARCH/build'
/sbin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-KZzuso/vmnet-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-KZzuso/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory '/tmp/modconfig-KZzuso/vmnet-only'
Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                            failed
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done
Unable to start services
 

Now I have the same failed communication interface also

   Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                            failed
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done
Unable to start services

PS, I have the vmware-patch 11.0.0-1 installed

Offline

#3 2019-04-17 18:01:24

lawndoc
Member
Registered: 2019-03-11
Posts: 3

Re: [vmware] Virtual machine communication interface failed

Did either of you ever figure out what was wrong? I am having the same issue.

Offline

#4 2019-04-17 20:36:33

HalosGhost
Forum Moderator
From: Twin Cities, MN
Registered: 2012-06-22
Posts: 2,093
Website

Re: [vmware] Virtual machine communication interface failed

lawndoc wrote:

Did either of you ever figure out what was wrong? I am having the same issue.

Hello. If you looked at the date of the thread, you'd see that is over four years old. If the issue you are having really is the same, likely the solution has even changed by this point.

At best, opening a new thread with all the relevant information to your problem, and referencing this old thread, is appropriate.

Please take this time to reread the Forum Etiquette and Code of Conduct (note that necrobumping is considered a violation of both).

Closing.

All the best,

-HG

Offline

Board footer

Powered by FluxBB