VMware Communities
VMWare9Help
Contributor
Contributor
Jump to solution

VMware Workstation 9: Could not open /dev/vmmon: No such file or directory

I am having a plethora of problems with installing and getting VMware Workstation 9 (9.0.2 build-1031769) to work on Ubuntu 13.04 (kernel 3.8.0-26-generic).

I have gone through exactly the same process on my laptop and it works perfectly, whereas on the desktop it seems everything breaks. Could someone give me some sort of help / hints on how I can go about getting this working. I have tried complete uninstall / reinstalls of the software, kernel headers, kernel images, different kernels, patches from here on fresh installs amongst everything else I can think of. Here's the issues I face in the order of importance (or so I think):

1) Whenever I try to open my virtual machine (and fresh ones), I get the error sequence of:

"Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded." -> "Failed to initialize monitor device." -> "Unable to change virtual machine power state: Cannot find a valid peer process to connect to"


2) Whenever I try to run the following command to setup the modules on a completely fresh setup (reinstalled kernel, vmware) I get the following output:

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-G9S0TM/vmmon-only'

/usr/bin/make -C /lib/modules/3.8.0-26-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

   MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/linux-headers-3.8.0-26-generic'

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

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

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

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

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

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

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

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

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

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

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

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

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

  Building modules, stage 2.

  MODPOST 1 modules

WARNING: "mcount" [/tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko] undefined!

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

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

make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-26-generic'

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

   MODULEBUILDDIR= postbuild

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

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

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

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

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

Using 2.6.x kernel build system.

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

/usr/bin/make -C /lib/modules/3.8.0-26-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

   MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/linux-headers-3.8.0-26-generic'

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

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

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

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

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

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

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

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

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

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

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

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

  Building modules, stage 2.

  MODPOST 1 modules

WARNING: "mcount" [/tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko] undefined!

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

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

make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-26-generic'

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

   MODULEBUILDDIR= postbuild

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

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

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

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

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

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-G9S0TM/vmblock-only'

/usr/bin/make -C /lib/modules/3.8.0-26-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

   MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/linux-headers-3.8.0-26-generic'

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/block.o

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/control.o

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.o

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/file.o

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/filesystem.o

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/inode.o

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/stubs.o

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/module.o

/tmp/modconfig-G9S0TM/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:

/tmp/modconfig-G9S0TM/vmblock-only/linux/control.c:285: warning: assignment from incompatible pointer type

/tmp/modconfig-G9S0TM/vmblock-only/linux/control.c:296: warning: passing argument 1 of ‘putname’ from incompatible pointer type

include/linux/fs.h:2052: note: expected ‘struct filename *’ but argument is of type ‘char *’

  CC [M]  /tmp/modconfig-G9S0TM/vmblock-only/linux/super.o

/tmp/modconfig-G9S0TM/vmblock-only/linux/inode.c:49: warning: initialization from incompatible pointer type

/tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.c:38: warning: initialization from incompatible pointer type

/tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:

/tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.c:104: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast

/tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.c:104: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’

  LD [M]  /tmp/modconfig-G9S0TM/vmblock-only/vmblock.o

  Building modules, stage 2.

  MODPOST 1 modules

WARNING: "mcount" [/tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!

WARNING: "putname" [/tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!

  CC      /tmp/modconfig-G9S0TM/vmblock-only/vmblock.mod.o

  LD [M]  /tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko

make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-26-generic'

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

   MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-G9S0TM/vmblock-only'

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

make[1]: Leaving directory `/tmp/modconfig-G9S0TM/vmblock-only'

cp -f vmblock.ko ./../vmblock.o

make: Leaving directory `/tmp/modconfig-G9S0TM/vmblock-only'

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-G9S0TM/vmci-only'

/usr/bin/make -C /lib/modules/3.8.0-26-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

   MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/linux-headers-3.8.0-26-generic'

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/linux/driver.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/linux/vmciKernelIf.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciContext.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciDatagram.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciDoorbell.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciDriver.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciHashtable.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciEvent.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciQPair.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciQueuePair.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciResource.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/common/vmciRoute.o

  CC [M]  /tmp/modconfig-G9S0TM/vmci-only/driverLog.o

  LD [M]  /tmp/modconfig-G9S0TM/vmci-only/vmci.o

  Building modules, stage 2.

  MODPOST 1 modules

WARNING: "mcount" [/tmp/modconfig-G9S0TM/vmci-only/vmci.ko] undefined!

  CC      /tmp/modconfig-G9S0TM/vmci-only/vmci.mod.o

  LD [M]  /tmp/modconfig-G9S0TM/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-26-generic'

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

   MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-G9S0TM/vmci-only'

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

make[1]: Leaving directory `/tmp/modconfig-G9S0TM/vmci-only'

cp -f vmci.ko ./../vmci.o

make: Leaving directory `/tmp/modconfig-G9S0TM/vmci-only'

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-G9S0TM/vsock-only'

/usr/bin/make -C /lib/modules/3.8.0-26-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

   MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/linux-headers-3.8.0-26-generic'

  CC [M]  /tmp/modconfig-G9S0TM/vsock-only/linux/af_vsock.o

  CC [M]  /tmp/modconfig-G9S0TM/vsock-only/linux/notify.o

  CC [M]  /tmp/modconfig-G9S0TM/vsock-only/linux/notifyQState.o

  CC [M]  /tmp/modconfig-G9S0TM/vsock-only/linux/stats.o

  CC [M]  /tmp/modconfig-G9S0TM/vsock-only/linux/util.o

  CC [M]  /tmp/modconfig-G9S0TM/vsock-only/linux/vsockAddr.o

  CC [M]  /tmp/modconfig-G9S0TM/vsock-only/driverLog.o

  LD [M]  /tmp/modconfig-G9S0TM/vsock-only/vsock.o

  Building modules, stage 2.

  MODPOST 1 modules

WARNING: "mcount" [/tmp/modconfig-G9S0TM/vsock-only/vsock.ko] undefined!

  CC      /tmp/modconfig-G9S0TM/vsock-only/vsock.mod.o

  LD [M]  /tmp/modconfig-G9S0TM/vsock-only/vsock.ko

make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-26-generic'

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

   MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-G9S0TM/vsock-only'

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

make[1]: Leaving directory `/tmp/modconfig-G9S0TM/vsock-only'

cp -f vsock.ko ./../vsock.o

make: Leaving directory `/tmp/modconfig-G9S0TM/vsock-only'

Starting VMware services:

   Virtual machine monitor                                            failed

   Virtual machine communication interface                            failed

   VM communication interface socket family                           failed

   Blocking file system                                                done

   Virtual ethernet                                                   failed

   VMware Authentication Daemon                                        done

Unable to start services

3) I often get Ubuntu "this program has crashed" messages about "/usr/lib/vmware-installer/2.1.0/vmis-launcher"" (this crash message always occurs when running the "vmware-modconfig" command above on a fresh install.

4) At various times when installing and having VMware workstation on my system I get Ubuntu crashes about "/usr/lib/vmware/bin/appLoader" and even "/bin/su" (especially when attempting to install - su NEVER crashes anywhere else).

Thoughts / ideas on what on earth is going on / what could have caused this all to go so downhill / how to go about fixing?

Thanks

Reply
0 Kudos
1 Solution

Accepted Solutions
VMWare9Help
Contributor
Contributor
Jump to solution

Solved.

The problem was that for another program I was using gcc-4.4 instead of the latest. Reverting the settings (through update-alternatives --config <name>) for gcc, g++ and cpp-bin.

Not a very graceful exit from having an invalid version I must say, maybe some sort of basic check could be added to ensure the correct versions are present?

View solution in original post

Reply
0 Kudos
3 Replies
julienvarela
Commander
Commander
Jump to solution

Hi,

Did you check this post ? : http://communities.vmware.com/thread/245998?start=0&tstart=0

Regards,

Julien

Regards, J.Varela http://vthink.fr
Reply
0 Kudos
VMWare9Help
Contributor
Contributor
Jump to solution

Yes I have, it also fails.

Whenever I run that sudo vmware-modconfig --console --install-all command I simply get an Ubuntu crash midway and the process fails like the output I have in the original post.

The Ubuntu crash is:

Sorry, the application vmis-launcher has stopped unexpectedly.

ExecutablePath

/usr/lib/vmware-installer/2.1.0/vmis-launcher

ProblemType

Crash

Title

vmis-launcher crashed with SIGSEGV in g_str_equal()

ProcCmdLine

/usr/lib/vmware-installer/2.1.0/vmis-launcher /usr/lib/vmware-installer/2.1.0/vmware-installer.py --register-file vmware-vmx regular /lib/modules/3.8.0-26-generic/misc/vmmon.ko


That's what I think are the important bits.

Reply
0 Kudos
VMWare9Help
Contributor
Contributor
Jump to solution

Solved.

The problem was that for another program I was using gcc-4.4 instead of the latest. Reverting the settings (through update-alternatives --config <name>) for gcc, g++ and cpp-bin.

Not a very graceful exit from having an invalid version I must say, maybe some sort of basic check could be added to ensure the correct versions are present?

Reply
0 Kudos