Hi folks,



We're discussing internally ways to solve this.

For now, you can actually work around it by running VMware Fusion as root.  To do so:

1) Open Terminal.app from the folder /Applications/Utilities.

2) At the Terminal prompt, type:

sudo "/Applications/VMware Fusion.app/Contents/MacOS/vmware"

3) Enter your password. 

Note: VMware Fusion will appear behind the Terminal window, and your list of VMs will be initially empty.  This is because root has a separate preferences list from the your normal user account.  You can use File -> Open to open a VM.

Note note: If you suspend the VM or take a snapshot, then those files will be owned by root, and you'll need to manually change the permissions from Finder to let your regular user use the VM.

Note note note: We do not suggest you should normally run VMware Fusion as root; this is just a workaround.  While we write very secure programs, it's possible for there to be a bug in the Fusion user interface that a malicious VM could exploit to gain privileges on your Mac.

Any progress on this?  This issue is driving me nuts.  I depend on using things like wireshark, and having to do sudo is not really working that well for me.

Eric

If you have a problem with direct Wifi bridging, I think Fusion will favor a "wired" connection over wireless, so you could try putting Fusion in bridged mode and enable Internet Sharing in OS X, sharing your Airport connection to Built-in Ethernet.  This activates en0 on the host without plugging a cable in, as far as VMware Fusion is concerned.  Before NAT was available this is how I would "fake" bridging.

Next steps I would take are attempting to restart Fusion networking (boot.sh --restart) or just reboot.  If problem persists, check disk permissions in Apple's Disk Utility and re-installing Fusion never hurts.

For me, launching vmware with sudo is working, although sort of inconvenient. My guest OS is Ubuntu 7.04, which doesn't seem to have any issues wrt promiscuous mode using this workaround.

However, our company is holding off upgrading to Leopard until this problem is resolved since VMWare Fusion is one of our primary applications. Hopefully there will be an update addressing this issue soon.

Add one more to the group - I am going to try the workaround in about 15 minutes but still, we need something easier and more reliable.

Any updates from VMWare?