Arch Linux

Fearce

Member

Registered: 2014-01-19

Posts: 19

[SOLVED] vmware not working

when i try to start a virtual machine i get 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 did everything the archwiki told me to do
i installed a patch and made a service for vmware that starts at startup
i think something is wrong with the service this is the service status:

[christian@revolution source]$ sudo systemctl status vmware -l
● vmware.service - VMware daemon
   Loaded: loaded (/etc/systemd/system/vmware.service; enabled)
   Active: active (exited) (Result: exit-code) since Fri 2014-04-04 15:51:15 CEST; 22h ago
  Process: 24759 ExecStart=/etc/init.d/vmware start (code=exited, status=1/FAILURE)
Main PID: 24759 (code=exited, status=1/FAILURE)
   CGroup: /system.slice/vmware.service

Apr 04 15:51:15 revolution systemd[1]: Started VMware daemon.
Apr 04 15:51:15 revolution vmware[24759]: Starting VMware services:
Apr 04 15:51:15 revolution vmware[24759]: [33B blob data]
Apr 04 15:51:15 revolution vmware[24759]: [50B blob data]
Apr 04 15:51:15 revolution vmware[24759]: [51B blob data]
Apr 04 15:51:15 revolution vmware[24759]: [30B blob data]
Apr 04 15:51:16 revolution vmware[24759]: [26B blob data]
Apr 04 15:51:16 revolution vmware[24759]: [38B blob data]
Apr 04 15:51:16 revolution systemd[1]: vmware.service: main process exited, code=exited, status=1/FAILURE
Apr 05 13:42:39 revolution systemd[1]: Started VMware daemon.

i had a lot of trouble gettinvmware to even start but after the patch vmware started normally but i cant run any virtual machines

Last edited by Fearce (2014-04-05 13:51:07)

Fearce

Member

Registered: 2014-01-19

Posts: 19

Re: [SOLVED] vmware not working

i have no idea why but after a restart it worked again

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,794

Re: [SOLVED] vmware not working

i have no idea why but after a restart it worked again

My guess would be that you had updated your kernel, but had not yet rebooted. 
Glad it is solved.  Please edit your first post and add [SOLVED] to the beginning of the thread's title.
(edit) Never mind --you had done that

Last edited by ewaller (2014-04-05 16:28:04)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way