In a new install, using an upgraded machine, the server fails to launch any vmx processes. After much fiddling, I can login to the console if I run it under sudo, but the machine "power on" button fails to accomplish anything. Like I said, there are NO vmware-vmx processes running; if I manually run them, I'm getting "Unexpected signal: 11."
The vmware-serverd.log file contains the error:
Feb 25 08:45:19: app| Connection from : /vmware/win2000Serv/win2000Serv.cfg
Feb 25 08:45:19: app| VMServerdConnect: connecting to /vmware/win2000Serv/win2000Serv.cfg
Feb 25 08:45:20: app| vmserverd: Could not connect to virtual machine /vmware/win2000Serv/win2000Serv.cfg: Unexpected response from vmware-authd: Error connecting to /usr/lib/vmware/bin/vmware-vmx process.
Feb 25 08:45:20: app| Failed to connect to vm: /vmware/win2000Serv/win2000Serv.cfg
Feb 25 08:45:20: app| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
Feb 25 08:45:20: app| VMHS: Connection to VM broken: cfg: /vmware/win2000Serv/win2000Serv.cfg; error: Pipe: Read failed; state: 3
also this comes from the debug vmware-vmx when manually run:
vmxvmdb: Index name being generated from config file
FILEIO: Unknown filesystem 0x3153464a for directory /var/run/vmware. Using non-linking locking.
FILEIO: Unknown filesystem 0x3153464a for directory /var/run/vmware. Using non-linking locking.
Accepted new connection at 45 for thread servercontrol (0x8390168)
Caught signal 11 -- tid 26344
Unexpected signal: 11.
Core dump limit is 0 kb.
Attempting to dump core...
Child process 26442 failed to dump core (status 0x6).
POST(no connection): VMware GSX Server unrecoverable error: (vmx)
Unexpected signal: 11.
A log file is available in "win2000Serv.log". Please request support and include the contents of the log file. We will respond on the basis of your support entitlement.
Any thoughts?[i][/i]