You are not logged in.
After upgrading Arch, my VMWare Workstation is failing to start virtual machines.
When powering on a VM, I get a popup window "Unable to change virtual machine power state: Cannot find a valid peer process to connect to". Interestingly, it works when I run VMWare as root.
Below are the log entries in /var/log/everything.log when I start up the VMWare UI:
Nov 21 11:14:37 w530 gnome-session[13684]: Logging to /tmp/vmware-ewebb/vmware-modconfig-14490.log
Nov 21 11:14:41 w530 [35968.908452] systemd[1]: Received SIGCHLD from PID 15145 (vmware-unity-he).
Nov 21 11:14:41 w530 [35968.908491] systemd[1]: Got SIGCHLD for process 15145 (vmware-unity-he)
Nov 21 11:14:41 w530 [35968.908570] systemd[1]: Child 15145 died (code=exited, status=1/FAILURE)
Nov 21 11:14:41 w530 [35969.004534] systemd[1]: Received SIGCHLD from PID 15152 (vmware-unity-he).
Nov 21 11:14:41 w530 [35969.004564] systemd[1]: Got SIGCHLD for process 15152 (vmware-unity-he)
Nov 21 11:14:41 w530 [35969.004636] systemd[1]: Child 15152 died (code=exited, status=1/FAILURE)
Nov 21 11:14:41 w530 [35969.072548] systemd[1]: Received SIGCHLD from PID 15159 (vmware-unity-he).
Nov 21 11:14:41 w530 [35969.072578] systemd[1]: Got SIGCHLD for process 15159 (vmware-unity-he)
Nov 21 11:14:41 w530 [35969.072660] systemd[1]: Child 15159 died (code=exited, status=1/FAILURE)
Nov 21 11:14:41 w530 [35969.167565] systemd[1]: Received SIGCHLD from PID 15166 (vmware-unity-he).
Nov 21 11:14:41 w530 [35969.167597] systemd[1]: Got SIGCHLD for process 15166 (vmware-unity-he)
Nov 21 11:14:41 w530 [35969.167681] systemd[1]: Child 15166 died (code=exited, status=1/FAILURE)
Nov 21 11:14:41 w530 [35969.242239] systemd[1]: Received SIGCHLD from PID 15173 (vmware-unity-he).
Nov 21 11:14:41 w530 [35969.242275] systemd[1]: Got SIGCHLD for process 15173 (vmware-unity-he)
Nov 21 11:14:41 w530 [35969.242370] systemd[1]: Child 15173 died (code=exited, status=1/FAILURE)
Nov 21 11:14:41 w530 [35969.316403] systemd[1]: Received SIGCHLD from PID 15182 (vmware-unity-he).
Nov 21 11:14:41 w530 [35969.316434] systemd[1]: Got SIGCHLD for process 15182 (vmware-unity-he)
Nov 21 11:14:41 w530 [35969.316508] systemd[1]: Child 15182 died (code=exited, status=1/FAILURE)
Nov 21 11:14:41 w530 [35969.374768] systemd[1]: Received SIGCHLD from PID 15191 (vmware-unity-he).
Nov 21 11:14:41 w530 [35969.374813] systemd[1]: Got SIGCHLD for process 15191 (vmware-unity-he)
Nov 21 11:14:41 w530 [35969.374899] systemd[1]: Child 15191 died (code=exited, status=1/FAILURE)
Nov 21 11:14:50 w530 /usr/lib/vmware/bin/vmware-hostd[10476]: Accepted password for user ewebb from 127.0.0.1
Nov 21 11:14:57 w530 [35984.669147] systemd[1]: Received SIGCHLD from PID 15851 (vmware-vmx).
Nov 21 11:14:57 w530 [35984.669174] systemd[1]: Got SIGCHLD for process 15851 (vmware-vmx)
Nov 21 11:14:57 w530 [35984.669220] systemd[1]: Child 15851 died (code=killed, status=4/ILL)Something with the vmware-unity-helper script is failing.
Any help with debugging steps is appreciated!
Offline
After digging more, it seems to be an nvidia and/or kernel issue. https://bbs.archlinux.org/viewtopic.php?id=173111 Downgrading back to 3.11 and nvida 325.15 got me back running,
Offline
Hello,
I'm also in this case. But I run 3.10.20 (LTS). Same error message if I install NVIdia proprietary drivers >319.49
Due to tearing issues, have to have 331.20.
Strangely, everything works fine (as user) if I run vmware from a terminal...
Offline
FYI, my log messages are a red-herring. VMWare now works after downgrading the kernel + nvidia, and everything.log looks the same.
Offline