MacOS – Vmware Fusion, how to remove suspend option completely

macosvmware

I have good number of virtual XP and W7 machines on our domain, one thing always cause problems when multiple users are using the same machine. There's always that one person whom put the vm session on suspend instead of shutdown. I know to change under preferences, but somehow users change default back to suspend. Is there a way to enforce shutdown only. this is the case for Fusion 5, 6.

thanks.

Best Answer

From Disabling the suspend feature for a virtual machine in VMware Fusion:

VMware Fusion

To disable the suspend feature for a virtual machine:

Shutdown the virtual machine.

Locate the virtual machine bundle. For more information, see Locating the virtual machine bundle in VMware Fusion (1007599).

Press Ctrl and click the virtual machine bundle, then click Show Package Contents.

Open the .vmx file for editing in a text editor. For more information, see Editing the .vmx file for your VMware Fusion virtual machine (1014782).

Add this line to the .vmx file:
suspend.disabled = "TRUE"

Save and close the .vmx file.

Restart the virtual machine.

Related Solutions

MacOS – Install Tiger in VMware Fusion

This article references VMware Workstation 6 as being able to run OS X with some hacks, but it's slow. But more importantly, that article runs down what I thought was the only known solution to running OS X in a VM: VirtualBox. So you aren't going to be able to do this with Fusion, but you can do it with VirtualBox.

Also: Apple does allow virtualization of OS X Server (check the date on that article - circa 2007). It honestly wouldn't stand much of a chance in the big, corporate IT world if it couldn't be legally virtualized these days.

Metasploit nmap VMware Fusion 5

For what its worth I've seen the same issue with Fusion 6 and nmap. I also saw tcpdump fail as well:

sudo tcpdump -i vmnet8
tcpdump: vmnet8: No such device exists
(BIOCSETIF failed: Device not configured)

After upgrading libpcap to 1.40 and this still not resolving the problem, I found the following outdated post: https://communities.vmware.com/message/693833#693833

Specifically this quote is where the issue lies: "No guarantees, but we can try to take a look at implementing BPF on Fusion's network interfaces in a future release."

This seems to point to the issue being a vmware problem, so I tried VirtualBox 4.3.0 and when using NAT at least, the issues do not occur (nmap also worked for me):

$ ifconfig
…
vboxnet0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:00:00:00:00
inet 192.168.56.1 netmask 0xffffff00 broadcast 192.168.56.255

$ sudo tcpdump -i vboxnet0
tcpdump: WARNING: vboxnet0: That device doesn't support promiscuous mode
(BIOCPROMISC: Operation not supported on socket)
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vboxnet0, link-type EN10MB (Ethernet), capture size 65535 bytes

Best Answer

Related Solutions

MacOS – Install Tiger in VMware Fusion

Metasploit nmap VMware Fusion 5

Related Question