Is there /any/ way I can override Fusion and * prevent* it from attaching darwin. If I move the darwin.iso file (or rename it to something other then darwin.iso), then Fusion complains about missing VMware Tools packages during bootup (I'm assuming it wants to attach the ISO file, which it can't find), and it takes 10 or so repeated 'OK' clicks to get the message to * go away*. After selecting the ESX/ESXi version, It will allow us to select the Operating system to download VMware tools ISO image version for the respective operating. Y ou can select the version of vSphere to download the VMware tools. And yet Fusion is insistent on attaching said ISO file during boot and booting from that, instead of my disk drive, which is royally screwing things up. Manually Download VMware Tools ISO Image.
I can't switch guestOS to anything other then 'darwin' or 'darwin-64'. Fusion then overrides any boot orders I've setup and the VM attemps to boot from this 'Darwin.iso' file instead of my disk drive. Apparently this is used as a sort of kludge bootloader for loading Mac OS X, since VMware's BIOS does not support booting OS X directly.
The family of POSIX standards is formally designated as IEEE 1003 and the ISO/. When guestOS is set to 'darwin', Fusion tries to automatically mount a file in' /Library/Application Support/VMware Fusion/isoimages' called 'Darwin.iso'. Originally, the name POSIX referred to IEEE Std 1003.1-1988, released in 1988. I'm running into a /highly/ annoying problem, however.
I've recently been trying to boot some custom Darwin-based VM's under OS X.
