Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 230613

VMWare Workstation 10.0.2 on Oracle Linux 3.8.13-26.2.3.el6uek.x86_64

$
0
0

Hello,

I have installed VMWare Workstation on Oracle Linux 3.8.13-26.2.3.el6uek.x86_64 Host.

 

The Virtual machine communication interface fails to start when starting the VMWare services:

[root@localhost ~]# /etc/init.d/vmware start

Starting VMware services:

   Virtual machine monitor                                 [  OK  ]

   Virtual machine communication interface                 [FAILED]

   VM communication interface socket family                [  OK  ]

   Blocking file system                                    [  OK  ]

   Virtual ethernet                                        [  OK  ]

   VMware Authentication Daemon                            [  OK  ]

[root@localhost ~]#


Same result when building VMWare configuration:

[root@localhost ~]# vmware-modconfig --console --install-all

Stopping VMware services:

   VMware Authentication Daemon                            [  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/modconfig-JD6ZLA/vmmon-only'

/usr/bin/make -C /lib/modules/3.8.13-26.2.3.el6uek.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

      MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/3.8.13-26.2.3.el6uek.x86_64'

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/linux/driver.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/linux/driverLog.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/linux/hostif.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/common/apic.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/common/comport.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/common/cpuid.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/common/memtrack.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/common/hashFunc.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/common/phystrack.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/common/task.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/common/vmx86.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmmon-only/vmcore/moduleloop.o

  SDTSTB  /tmp/modconfig-JD6ZLA/vmmon-only/vmmon.sdtstub.S

  AS [M]  /tmp/modconfig-JD6ZLA/vmmon-only/vmmon.sdtstub.o

  LD [M]  /tmp/modconfig-JD6ZLA/vmmon-only/vmmon.o

  Building modules, stage 2.

  MODPOST 1 modules

  SDTINF  /tmp/modconfig-JD6ZLA/vmmon-only/vmmon.sdtinfo.c

  CTF

  CC      /tmp/modconfig-JD6ZLA/vmmon-only/vmmon.mod.o

global:0:CPUID_INTERNAL_ECXIN_TOPOLOGY_LEVEL_NUMBER: CTF error in assembly of item with tag 40: Limit on number of dynamic type members reached

global:0:CPUID_INTERNAL_ECXIN_TOPOLOGY_LEVEL_NUMBER: CTF error in assembly of item with tag 40: Limit on number of dynamic type members reached

global:0:CPUID_INTERNAL_ECXIN_TOPOLOGY_LEVEL_NUMBER: CTF error in assembly of item with tag 40: Limit on number of dynamic type members reached

global:0:CPUID_INTERNAL_ECXIN_TOPOLOGY_LEVEL_NUMBER: CTF error in assembly of item with tag 40: Limit on number of dynamic type members reached

4 CTF construction errors.

  LD [M]  /tmp/modconfig-JD6ZLA/vmmon-only/vmmon.ko

make[1]: Leaving directory `/usr/src/kernels/3.8.13-26.2.3.el6uek.x86_64'

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

      MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-JD6ZLA/vmmon-only'

make[1]: `postbuild' is up to date.

make[1]: Leaving directory `/tmp/modconfig-JD6ZLA/vmmon-only'

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory `/tmp/modconfig-JD6ZLA/vmmon-only'

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-JD6ZLA/vmnet-only'

/usr/bin/make -C /lib/modules/3.8.13-26.2.3.el6uek.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

      MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/3.8.13-26.2.3.el6uek.x86_64'

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/driver.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/hub.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/userif.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/netif.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/bridge.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/filter.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/smac_compat.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/procfs.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/smac.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/vnetEvent.o

  CC [M]  /tmp/modconfig-JD6ZLA/vmnet-only/vnetUserListener.o

  SDTSTB  /tmp/modconfig-JD6ZLA/vmnet-only/vmnet.sdtstub.S

  AS [M]  /tmp/modconfig-JD6ZLA/vmnet-only/vmnet.sdtstub.o

  LD [M]  /tmp/modconfig-JD6ZLA/vmnet-only/vmnet.o

  Building modules, stage 2.

  MODPOST 1 modules

  SDTINF  /tmp/modconfig-JD6ZLA/vmnet-only/vmnet.sdtinfo.c

  CTF

  CC      /tmp/modconfig-JD6ZLA/vmnet-only/vmnet.mod.o

  LD [M]  /tmp/modconfig-JD6ZLA/vmnet-only/vmnet.ko

make[1]: Leaving directory `/usr/src/kernels/3.8.13-26.2.3.el6uek.x86_64'

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

      MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-JD6ZLA/vmnet-only'

make[1]: `postbuild' is up to date.

make[1]: Leaving directory `/tmp/modconfig-JD6ZLA/vmnet-only'

cp -f vmnet.ko ./../vmnet.o

make: Leaving directory `/tmp/modconfig-JD6ZLA/vmnet-only'

Starting VMware services:

   Virtual machine monitor                                 [  OK  ]

   Virtual machine communication interface                 [FAILED]

   VM communication interface socket family                [  OK  ]

   Blocking file system                                    [  OK  ]

   Virtual ethernet                                        [  OK  ]

   VMware Authentication Daemon                            [  OK  ]

Unable to start services

[root@localhost ~]#

 

Hence, starting a virtual machine in VMWare Workstation reports the error "Failed to open device "/dev/vmci": No such file or directory Please make sure that the kernel module 'vmci' is loaded. Module DevicePowerOn power on failed. Failed to start the virtual machine."

 

I have been googling on the various slogans (e.g. vmci, /dev/vmci, virtual machine communication interface failing, vmci and linux kernel 3.8.13, ...) for many, many hours but none of the results and suggested resolutions fixed the problem. Some topics explained that both virtual machine communication interface and VM communication interface socket family fail to start, but for me only the Virtual machine communication interface fails. Some other topics explains issues with Linux kernel 3.8.13 (or Linux kernel 3.13 / 3.14), but the suggested actions does not resolve the problem in starting the virtual machine communication interface I am experiencing.

 

Find attached some more logfiles I think are relevant. Please tell me if any more logfiles are needed.

 

Any suggestions how to resolve this problem?

 

Many Thanks,

 

Antoon.


Viewing all articles
Browse latest Browse all 230613

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>