The virtual machine's operating system has attempted to enable promiscuous mode on adapter Ethernet0. This is not allowed for security reasons.

[sefsinc]

Hi all,

When I start my vm I am getting the error

"The virtual machine's operating system has attempted to enable promiscuous mode on adapter Ethernet0. This is not allowed for security reasons."

I have been to this page http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=287

From this page, on my host I have created a group called "vmware-vmnet0", I then add the user running vmware to this group. I then give this group rw permissions on /dev/vmnet0

However I still get the same error above on booting the vm everytime. How can I solve this very bad problem.

Thanks.

[louyo]

Since no one else has jumped in yet, I will give my very limited experience with this.

I have only seen that when I ran a VM, using bridged NIC, that needed promiscuous mode. doing:

sudo chmod a+rw /dev/vmnet0

from a terminal resolved it. Did you try that?

KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=287, that KB references

http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=514

perhaps your network adapter does not support promiscuous mode?

Lou

[sefsinc]

Indeed it does,

The problem i see is that when ever I reboot the host machine the permissions I added to vmnet0 are reverted to root:root instead of the root:vmware-vmnet0 I had set!

I wonder why it would do that.

[admin · Accepted solution]

Device nodes are recreated at boot time. You can thank Linux udev. To work around this, create the vmnet* devices with the ownership and permissions you want under /lib/udev/devices.

[sefsinc]

You are on the ball there sire. A big thank you for that.

--- this bit is just to make sure this is well covered in the forums by being mentioned multiple times in various threads. ---

This tread showed me how to create the devices in /lib/udev/devices ( http://communities.vmware.com/message/460583#460583 )

Which was to run this command

cp -rp /dev/vmnet0 /lib/udev/devices/

and then set the approriate permissions for group ownershi.

[sefsinc]

I need some assistance again. I performed this operation in Jaunty. But I cannot get it duplicated in Karmic.

What I did was ...

1) create a group called vmware-vmnet0

2) Add my user to this group

3) cp -rp /dev/vmnet0 /lib/udev/devices/

4) Set Goup ownership of /lib/udev/devices/vmnet0 to vmware-vmnet0 andghen give it rw for this group

5) rm /dev/vmnet0

6) reboot

But /dev/vmnet0 always comes back as root:root

Can someone lead me thru this again.

Thanks.