Update: Mark Wilson has gone through this with a more recent version of VMware, and his article is likely to be more useful.
Regarding this piece, thanks to Chris Dagdigian for pointing out the need for trusted X forwarding.
So, with every release, I kept trying to find a way to both see and control my virtual machine consoles by running vmware-console on the server and forwarding the X display to my Mac - which never seemed to work due to various X11 quirks - either the application bombed instantly, or there were masses of debug logging - but never a working remote console.
However, after months of virtual head-banging, Chris Dagdigian e-mailed me a note saying that he had got his vmware-console running by using trusted X forwarding, and after a while I had the rest figured out - keyboard mappings and all.
On The VMware Host
You then have to edit ~/.vmware/preferences to set that keyboard map:
...and pay attention to the vmware-console output.
On Mac OS X:
monotith:~ user$ ssh -Y [email protected] Last login: Sun Mar 12 21:42:49 2006 from monolith.internal.taoofmac.com [[email protected] ~]$ vmware-console
And presto, it should appear on your X11 display. There is a very important point that needs stressing, though -
If VMware is unable to detect your keyboard settings, you won't be able to control guest virtual machines properly - you won't even be able to see the console.
Hence the importance of setting the keymap properly. You might also want to remember that some key combos are slightly different on the Mac - for instance, Ctrl+Alt to exit a VM is actually Ctrl+Command, etc., etc.
Regarding xauth and X11.app in other contexts, some people have noted that xauth usually works for them after issuing the following command in xterm:
xauth generate :0 . trusted
Although I've yet to establish a relationship, it seems to have helped me as well.