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.

For the last 2 days we were having network connectivity trouble with our clients. It appears to be an issue with DHCP requests from different VLANS to a virtual machine running a DHCP server. I’m not sure it’s caused by ESX’s virtual networking or ESX’s interaction with our Cisco equipment. I have had this issue with both Windows 2000 Server and Windows Server 2003’s DHCP servers. It would be interesting to know if a Linux server would have the same issue. I have had this issue a few times, once when we first setup our virtual infrastructure and again just this week after I rebooted the DHCP server.

Problem:

Clients that were rebooted were not able to logon properly or surf the internet, they effectively dropped off the network. Clients were receiving IP addresses that were not for their VLAN. For example, clients in the 10.80.8.x/21 subnet were getting 10.80.0.x/21 addresses. These clients were only able to ping the DHCP server.

Solution:

1. Open Virtual Infrastructure Client
2. Find & select virtual machine running DHCP
3. “Edit Settings” on virtual machine
4. Select network adapter used for DHCP
5. Uncheck “Connected”
6. Click “OK”
7. “Edit Settings” on virtual machine again
8. Select network adapter used for DHCP
9. Check “Connected”
10. Click “OK”

Essentially you are resetting the network connection. I don’t know why this works, but I’d like to know!