A tip or two for VMware Fusion (OS X) guest networking

Before I get into this post too far, yes, I’m now a Mac user. Not exactly a fanboy yet, but my new employer let me choose between a Windows laptop and a MacBook for my work computer, so I chose–wisely. I’d been using Ubuntu on an HP laptop (ugh to HP) for a few years, so it seemed like a chance to try something new at no cost to me, which is my favorite cost.

As you can see from my other posts about virtualization, I’m a big fan of Virtualbox, but this post is about VMware Fusion, which was provided to me with my MacBook.

On to the tips…

I’ve been creating a testing environment for tacacs+ servers for a Cisco networking environment as well as Puppet server management, and I’m horrible with remembering IP addresses, unless there’s a very distinct pattern. When you use NAT in Fusion, addresses are assigned to guests VMs via DHCP in an automatically generated scope. The problem is, every time you boot your server you may get a new DHCP address! That sucks.

What to do?

Read more

Virtualbox 4.0 = good stuff

Virtualbox is definitely my favorite virtualization tool. Yes, I know there are other, more popular ones, but Virtualbox is free, runs on many platforms, and isn’t clunky to use, like some unnamed others. We all have our preferences, and Virtualbox is definitely mine.

I haven’t had a lot of time to kick the tires yet, but one of the best features I’ve found in the latest, 4.0, version is an easy method to export virtual machines that you’ve built. There were ways to do it before, but now it’s easy.

Once you’ve installed/upgraded to version 4.0, simply choose Export Appliance from the File menu of the Virtualbox Manager. The first one I did took less than 10 minutes from start to finish, all wrapped-up in a single file.

Like I said: good stuff.