Gorillapond Dot Com

I was excited to see VMware Fusion released last week, since I missed getting into the private beta. It was a fairly large download, about the size as VMware Workstation. After the painless installation process, I copied over some of my template VMDKs for Windows XP and Server 2003 to my MacBook so I could get going as soon as possible. I started up VMware Fusion, nice interface, very clean. Now to get down to business.

I didn’t get very far. To get Fusion working at this point as intended, you must do a CD install. I’ll probably do that at some point, but.. what a bummer.

The “New Virtual Machine” wizard was a bit too friendly for me, and didn’t offer any custom or advanced choice. It felt like the old Virtual PC for PowerPC Macs. No option to connect a template drive to the new virtual machine like I can do in VMware Workstation. Oh well, I thought I would just create a blank drive and edit the virtual machine once it’s created.

Nope, the virtual machine configuration editor is essentially useless. All the options “will be editable in a future release.” No way to attach my template VMDKs. It appears that I could edit the VMX file manually, but that’s a lot of extra work! You also get a warning about debug mode, which was enabled on VMware Server.

I plan to use Fusion in my presentations instead of bringing an extra notebook to connect to the projector, I hope it becomes more functional before mid February!

Update: I took my blank VM, renamed the blank VMDK file and replaced it with my template Windows XP VMDK by renaming the template to the old file name and placing it in the virtual machine’s folder. I booted it up and it worked like a charm.