Hi,
Everything works fine when i start vmware workstation (or vmplayer) as ROOT,but as a normal user it pops up a dialog and all my vms failed to power on:
"Unable to change virtual machine power state: Cannot find a valid peer process to connect to"
I've tried reinstalling vmware-workstation 10.0.1 and vmware-workstation 9.0.2,nothing helps for this situation.
any kind of help would be much appreciated. (it really drives me mad:()
[hillbilly@WS ~]$ ls -la /usr/lib/vmware/bin/vmware-vmx
-rwsr-xr-x 1 root root 14494744 Nov 16 12:12 /usr/lib/vmware/bin/vmware-vmx
[hillbilly@WS ~]$ ls -la /var/run/vm*
srwxrwxrwx 1 root root 0 Nov 16 12:25 /var/run/vmnat.14443
-rw-rw-rw- 1 root root 6 Nov 16 12:25 /var/run/vmnet-bridge-0.pid
-rw-r----- 1 root root 6 Nov 16 12:25 /var/run/vmnet-dhcpd-vmnet1.pid
-rw-r----- 1 root root 6 Nov 16 12:25 /var/run/vmnet-dhcpd-vmnet8.pid
-rw-r--r-- 1 root root 6 Nov 16 12:25 /var/run/vmnet-natd-8.pid
-rw-rw-rw- 1 root root 6 Nov 16 12:25 /var/run/vmnet-netifup-vmnet1.pid
-rw-rw-rw- 1 root root 6 Nov 16 12:25 /var/run/vmnet-netifup-vmnet8.pid
/var/run/vmblock-fuse:
total 0
dr-xr-xr-x 3 root root 4096 Nov 16 12:45 .
drwxr-xr-x 23 root root 780 Nov 16 12:28 ..
dr-xr-xr-x 3 root root 4096 Nov 16 12:45 blockdir
-rw------- 1 root root 0 Nov 16 12:45 dev
/var/run/vmware:
total 0
drwxr-xr-x 4 root users 100 Nov 16 12:40 .
drwxr-xr-x 23 root root 780 Nov 16 12:28 ..
lrwxrwxrwx 1 root users 53 Nov 16 12:40 73641d12dd845ac480cee34457fedc8c -> /var/run/vmware/hillbilly_1000/1384576859410364_20339
drwx------ 3 hillbilly users 60 Nov 16 12:40 hillbilly_1000
drwx------ 2 root root 40 Nov 16 12:40 root_0
in the UI log:
2013-11-16T12:50:18.047+08:00| vmui| I120: VMHSVMCbPower: /home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx, Setting state of VM to powerOn with option hard
2013-11-16T12:50:18.047+08:00| vmui| I120: Starting vmx as /usr/lib/vmware/bin/vmware-vmx
2013-11-16T12:50:18.047+08:00| vmui| I120: Starting vmx as /usr/lib/vmware/bin/vmware-vmx
2013-11-16T12:50:18.047+08:00| vmui| I120: /home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx: VMHS: VM /home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx in directory /home/hillbilly/vmware/BT5R3-GNOME-VM-32
2013-11-16T12:50:18.047+08:00| vmui| I120: /home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx: VMHS: Exec()'ing /usr/lib/vmware/bin/vmware-vmx.
2013-11-16T12:50:18.052+08:00| vmui| I120: VmdbAddConnection: cnxPath=/db/connection/#57e/, cnxIx=3
2013-11-16T12:50:18.052+08:00| vmui| I120: Vmdb_AddConnectionAsync_Secure: registered VERSION completion callback, cnx = /db/connection/#57e/
2013-11-16T12:50:18.087+08:00| vmui| I120: OnVMStateChanged
2013-11-16T12:50:18.087+08:00| vmui| I120: SetAttached
2013-11-16T12:50:18.088+08:00| vmui| I120: OnSetAttachedCompleted
2013-11-16T12:50:18.286+08:00| vmui| I120: /home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx: Mounting virtual machine paths on connection: /db/connection/#57e/.
2013-11-16T12:50:18.287+08:00| vmui| I120: VmdbCnxControlCb: registered SUBSCRIBE completion callback, cnx = /db/connection/#57e/
2013-11-16T12:50:18.468+08:00| vmui| I120: VmdbPipeStreamsOvlError Couldn't read: (104) Connection reset by peer.
2013-11-16T12:50:18.468+08:00| vmui| I120: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#57e/' (-32)
2013-11-16T12:50:18.470+08:00| vmui| I120: VigorClientStartMountCb Failed: Pipe: Read failed
2013-11-16T12:50:18.470+08:00| vmui| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#57e/'
2013-11-16T12:50:18.471+08:00| vmui| I120: VmdbCtxCheckOneof: One-of: /db/connection/#57e/type/ sub []
2013-11-16T12:50:18.471+08:00| vmui| I120: Vmdb_Unset failed: /db/connection/#57e/type/sub/mountState/req/#57f/ (A one-of constraint has been violated)
2013-11-16T12:50:18.471+08:00| vmui| I120: Vmdb_Unset failed: /db/connection/#57e/type/sub/mountState/req/#57f/ (A one-of constraint has been violated)
2013-11-16T12:50:18.471+08:00| vmui| I120: /home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx: Reloading config state.
2013-11-16T12:50:18.476+08:00| vmui| I120: VMHS: Transitioned vmx/execState/val to poweredOff
2013-11-16T12:50:18.516+08:00| vmui| I120: SnapshotTree: Populating (/home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx)
2013-11-16T12:50:18.517+08:00| vmui| I120: SnapshotTree: Emitting refresh (/home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx)
2013-11-16T12:50:18.541+08:00| vmui| I120: Setting power state poweredOff
2013-11-16T12:50:18.546+08:00| vmui| I120: Vix: [19796 foundryVMPowerOps.c:980]: FoundryVMPowerStateChangeCallback: /home/hillbilly/vmware/BT5R3-GNOME-VM-32/BT5R3-GNOME-VM-32.vmx, vmx/execState/val = poweredOff.
2013-11-16T12:50:18.563+08:00| vmui| I120: OnVMStateChanged
Hi Knell!
Can you see if there is a /home/hillbilly/vmware/BT5R3-GNOME-VM-32/vmware.log created after you try to power on the VM? If so, kindly attach it to a reply here. (To attach a log file to your post, choose Use advanced editor in the top-right corner of the composer, then use the Browse... button below and select the file.)
Cheers,
--
Darius
I had the same problem and found that I was hitting the maximum allowed open files. Try increasing your settings in /etc/security/limits.conf , for example :
hillbilly soft nofile 65536
hillbilly hard nofile 65536
Then log out and log back in.
I have the same problem, in the vmware-ui-xxxx.log:
2013-11-22T17:34:28.798+01:00| vmui| I120: Starting vmx as /opt/vmware/lib/vmware/bin/vmware-vmx
2013-11-22T17:34:28.798+01:00| vmui| I120: Starting vmx as /opt/vmware/lib/vmware/bin/vmware-vmx
2013-11-22T17:34:28.798+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: VMHS: VM /home/herve/vmware.newvms/Windows 7/Windows 7.vmx in directory /home/herve/vmware.newvms/Windows 7
2013-11-22T17:34:28.798+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: VMHS: Exec()'ing /opt/vmware/lib/vmware/bin/vmware-vmx.
2013-11-22T17:34:28.803+01:00| vmui| I120: VmdbAddConnection: cnxPath=/db/connection/#ae/, cnxIx=1
2013-11-22T17:34:28.803+01:00| vmui| I120: Vmdb_AddConnectionAsync_Secure: registered VERSION completion callback, cnx = /db/connection/#ae/
2013-11-22T17:34:28.817+01:00| vmui| I120: OnGuestCanRunUnityChanged: OS is not old Windows, checking Tools status. Version status: 5, running status: 1
2013-11-22T17:34:28.817+01:00| vmui| I120: OnGuestCanRunUnityChanged: Tools status is not INSTALLED
2013-11-22T17:34:28.843+01:00| vmui| I120: OnVMStateChanged: alive = 1
2013-11-22T17:34:28.843+01:00| vmui| I120: SetAttached: detach
2013-11-22T17:34:28.843+01:00| vmui| I120: OnSetAttachedCompleted
2013-11-22T17:34:28.911+01:00| vmui| I120: VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF, (11) Ressource temporairement non disponible.
2013-11-22T17:34:28.911+01:00| vmui| I120: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#ae/' (-32)
2013-11-22T17:34:28.915+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Mounting VM begun.
2013-11-22T17:34:28.915+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Mounting virtual machine paths on connection: /db/connection/#ae/.
2013-11-22T17:34:28.918+01:00| vmui| I120: VigorClientStartMountCb Failed: Pipe connection has been broken
2013-11-22T17:34:28.918+01:00| vmui| I120: VigorClientDisconnect: disconnect /vm/#44d1d136bdac4d2d/ via /db/connection/#ae/
2013-11-22T17:34:28.918+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Unmounting VM begun.
2013-11-22T17:34:28.918+01:00| vmui| I120: VMDB not mounted for /vm/#44d1d136bdac4d2d/.
2013-11-22T17:34:28.918+01:00| vmui| I120: VigorClientUnmountCb: Mount state values have changed for /vm/#44d1d136bdac4d2d/.
2013-11-22T17:34:28.918+01:00| vmui| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#ae/'
2013-11-22T17:34:28.919+01:00| vmui| I120: VigorClientUnmountCb: Unmount complete for /vm/#44d1d136bdac4d2d/.
2013-11-22T17:34:28.919+01:00| vmui| I120: VigorClientUnmountCb unset Vigor path on vm unmount.
2013-11-22T17:34:28.919+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Unmounting VM complete.
2013-11-22T17:34:28.919+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Pending power op found, completing.
2013-11-22T17:34:28.919+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Clearing execReqPath
2013-11-22T17:34:28.919+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Reloading config state.
2013-11-22T17:34:28.928+01:00| vmui| I120: VMHS: Transitioned vmx/execState/val to poweredOff
2013-11-22T17:34:28.931+01:00| vmui| I120: VmdbCtxCheckOneof: One-of: /db/connection/#ae/type/ sub []
2013-11-22T17:34:28.931+01:00| vmui| I120: Vmdb_Unset failed: /db/connection/#ae/type/sub/mountState/req/#af/ (A one-of constraint has been violated)
2013-11-22T17:34:28.931+01:00| vmui| I120: Vmdb_Unset failed: /db/connection/#ae/type/sub/mountState/req/#af/ (A one-of constraint has been violated)
2013-11-22T17:34:28.931+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: VMHSStartVmxVigorCb: vmPath=/vm/#44d1d136bdac4d2d/ status=error
2013-11-22T17:34:28.931+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Reloading config state.
2013-11-22T17:34:28.940+01:00| vmui| I120: VMHS: Transitioned vmx/execState/val to poweredOff
2013-11-22T17:34:28.943+01:00| vmui| I120: Internal VMDB error: VMDB failure (-1)
But, I can start the vmware machine with sudo vmware !
I'm having a hard time with this very same issue too, increasing the file limit doesn't seem to do the trick, thanx tho
Got this issue fixed by downgrading my linux kernel from 3.12.2.1 to 3.11.6.1 it also required downgrading my nvidia drivers, libgl and utils from 331.20.1 to 325.15.1 because the 331 drivers require kernel 3.12
I'm pretty sure the issue is caused by the 3.12 kernel but further testing must be done to probe that.
all this was tested on ARCH Linux
ctorresc wrote: I'm pretty sure the issue is caused by the 3.12 kernel but further testing must be done to probe that.
As a general rule with supported Linux distros, initially only the release kernel is supported and if running newer kernels it may require third-party patches until VMware releases an update/upgrade containing support for newer kernels in supported Linux distros. That doesn't necessarily mean that only the release kernel will work however newer kernels tend to quickly break some aspect of VMware products!