problem after update vmware

Message

esperto · Post by **esperto** » Sat Oct 08, 2005 12:45 am

I update vmware to vmware-workstation-5.0.0.13124-r2, sisce then I can only start a VM when I run it as root, if I run as my regular user I get a error message that said "Unable to change virtual machine power state: Failed to connect to peer process.", it was working perfectly before the update, and I've already add vmware to the list of my user group.
looking at other forums some people said that they have the same problem and could resolve it adding execution bit (other) to permissions for /opt/vmware/lib/bin/vmware-vmx, I did it, but nothing happens...
I've already reemerged 2 times...

someone knows what maybe happining?

rickvernam · Post by **rickvernam** » Sat Oct 08, 2005 2:56 am

You know, I had this problem too.
But, I cannot remember what I did to fix it. I will find it eventually and let you know...

For some reason, I'm thinking that it was something stupid like getting rid of ~/.vmware (or even better, rename it to something... maybe ~/.vmware-old or whatever works for you)...

In any case, I'm going to figure this out & let you know what I find...

rickvernam · Post by **rickvernam** » Sat Oct 08, 2005 3:04 am

hmm...I just found what I was looking for, but then realized after reading your post again that you already tried doing what I was thinking of...
So I'm all out of ideas.

brankob · Post by **brankob** » Sat Oct 08, 2005 3:43 am

Could it be that it is something related to kernel "capabilities" ( look under make menuconfig --> security) ?

I had similar problem with jack. before compiling-in capabilites I coudn't run it with --realtime as a non-root...

Kerthale · Post by **Kerthale** » Sat Oct 08, 2005 1:47 pm

This issue is discussed on other places on the forum aswell, so it's not an AMD64 issue. You can search the forums for it. I believe the actual solution was to add the user to the vmware group and to do this to fix the permissions:

Code: Select all

chmod +s /opt/vmware/lib/bin/vmware-vmx

druggo · Post by **druggo** » Sat Oct 08, 2005 1:49 pm

I got the same error message, but I never update it, just change to a user ...

esperto · Post by **esperto** » Sat Oct 08, 2005 1:53 pm

I don't know why, but when I boot up today vmware was working again... maybe I needed reload something that I didn't and the boot did... anyway thanks for the help

scooper · Post by **scooper** » Sat Oct 08, 2005 9:00 pm

FWIW - I had the same problem. I think it went away after device permissions were fixed on /dev/vmnet*, or something like that.

Hope that helps (at least for future reference).
Steve

chetan13 · Post by **chetan13** » Sun Oct 09, 2005 2:50 am

I think you should add your username to the "vmware" group in /etc/group
It worked for me when i did that

Lars · Post by **Lars** » Mon Oct 10, 2005 8:26 am

Ok, I add myself to vmware group I add the follows line

Code: Select all

vmware:x:56401:lars

and store it in /etc/group
file, but what I have to do now, so a simple id or groups show me that I'm really in the group 'vmware', without reboot please?

brankob · Post by **brankob** » Mon Oct 10, 2005 8:34 am

I usually have to reboot when changing secondary group ownership.