pjkelly · July 7, 2011 01:06 · Jul 7, 2011 · Jul 7, 2011 · Jul 7, 2011 · Jul 7, 2011
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -36,7 +36,7 @@ Take note of the line starting with `range`.  The IP addresses you will assign y
 ####### VMNET DHCP Configuration. End of "DO NOT MODIFY SECTION" #######
 ```
 
-Below that line, add a clause for you guest machine.  It should look like this:
+Below that line, add a clause for your guest machine.  It should look like this:
 
 ```
 host ubuntu-lucid-lynx-base {

diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -1,6 +1,6 @@
 # How to setup your VMWare Fusion images to use static IP addresses on Mac OS X
 
-At [Crush + Lovely](http://crushlovely.com), we use [Railsmachine's](http://railsmachine.com) Moonshine to automate the configuration of our servers.  When writing our deployment recipes, VMWare Fusion's ability to take snapshots and rollback to these snapshots is a huge timesaver because it takes just seconds to roll a server image to it's original state.
+At [Crush + Lovely](http://crushlovely.com), we use [Railsmachine's](http://railsmachine.com) [Moonshine](http://github.com/railsmachine/moonshine) to automate the configuration of our servers.  When writing our deployment recipes, VMWare Fusion's ability to take snapshots and rollback to these snapshots is a huge timesaver because it takes just seconds to roll a server image to it's original state.
 
 When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them.  While not documented well at all, it turns out that this is relatively easy to accomplish in four simple steps.
 

diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -9,10 +9,10 @@ When you're just configuring a single server, having a static IP address for you
 Let's say you have a guest machine with the name `ubuntu-lucid-lynx-base` and you keep your guest machine images in `~/Documents/Virtual\ Machines/`.  To determine the MAC address for this VM, you can run:
 
 ```
-cat ~/Documents/Virtual\ Machines/ubuntu-lucid-lynx-base/ubuntu-lucid-lynx-base.vmx
+cat ~/Documents/Virtual\ Machines/ubuntu-lucid-lynx-base.vmwarevm/ubuntu-lucid-lynx-base.vmx | grep ethernet0.generatedAddress
 ```
 
-Get the Ethernet MAC address from ifconfig eth0 inside the guest machine, or from ~/Documents/Virtual Machines/GUESTMACHINENAME/GUESTMACHINENAME.vmx (it’s the line with ethernet0.generatedAddress).
+If more than one line is returned, you're looking for the one with the value like `00:0c:29:9d:2a:38`.
 
 ## 2. Add your static IP address to VMWare's `dhcpd.conf`
 
@@ -30,11 +30,38 @@ subnet 172.16.179.0 netmask 255.255.255.0 {
 }
 ```
 
-Take note of the line starting with `range`.  The IP addresses you will assign your guest machines will need to fall *outside* that range.
+Take note of the line starting with `range`.  The IP addresses you will assign your guest machines will need to fall *outside* that range.  Find the line that looks like this:
 
-## 3. Update your `/etc/hosts` file to assign your guest machine with a static IP address a fancy hostname.
+```
+####### VMNET DHCP Configuration. End of "DO NOT MODIFY SECTION" #######
+```
+
+Below that line, add a clause for you guest machine.  It should look like this:
+
+```
+host ubuntu-lucid-lynx-base {
+    hardware ethernet 00:0c:29:9d:2a:38;
+    fixed-address 172.16.179.102;
+}
+```
+
+Make sure the `hardware ethernet` value matches the MAC address you found in step one, and the `fixed-address` is an IP outside the range listed in the `subnet` clause.
+
+## 3. Optional: Update your `/etc/hosts` file
+
+If you want to assign a fancy local hostname that refers to your guest machine, you can do so by editing your `/etc/hosts` file.  For instance, to assign the hostname `ubuntu.local` to the guest machine we just setup, we could add the following line to our `/etc/hosts` file:
+
+```
+172.16.179.102 ubuntu.local
+```
 
 ## 4. Restart the VMWare daemons
 
-* _source_: http://crshlv.ly/rjlXdS
+Last thing to do is restart your VMWare daemons:
+
+```
+sudo "/Library/Application\ Support/VMware\ Fusion/boot.sh" --restart
+```
+
+* _original source_: http://crshlv.ly/rjlXdS
 * _note_: These instructions have been tested on Snow Leopard only.
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -4,7 +4,15 @@ At [Crush + Lovely](http://crushlovely.com), we use [Railsmachine's](http://rail
 
 When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them.  While not documented well at all, it turns out that this is relatively easy to accomplish in four simple steps.
 
-## 1. Determine the mac address of your guest machine
+## 1. Determine the MAC address of your guest machine
+
+Let's say you have a guest machine with the name `ubuntu-lucid-lynx-base` and you keep your guest machine images in `~/Documents/Virtual\ Machines/`.  To determine the MAC address for this VM, you can run:
+
+```
+cat ~/Documents/Virtual\ Machines/ubuntu-lucid-lynx-base/ubuntu-lucid-lynx-base.vmx
+```
+
+Get the Ethernet MAC address from ifconfig eth0 inside the guest machine, or from ~/Documents/Virtual Machines/GUESTMACHINENAME/GUESTMACHINENAME.vmx (it’s the line with ethernet0.generatedAddress).
 
 ## 2. Add your static IP address to VMWare's `dhcpd.conf`
 

diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -2,9 +2,13 @@
 
 At [Crush + Lovely](http://crushlovely.com), we use [Railsmachine's](http://railsmachine.com) Moonshine to automate the configuration of our servers.  When writing our deployment recipes, VMWare Fusion's ability to take snapshots and rollback to these snapshots is a huge timesaver because it takes just seconds to roll a server image to it's original state.
 
-When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them.
+When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them.  While not documented well at all, it turns out that this is relatively easy to accomplish in four simple steps.
 
-Now open `/Library/Application\ Support/VMware\ Fusion/vmnet8/dhcpd.conf`. `vmnet8` is the virtual interface for NAT networking in VMWare the guest machines.  In this file, you'll see a subnet clause that looks something like this:
+## 1. Determine the mac address of your guest machine
+
+## 2. Add your static IP address to VMWare's `dhcpd.conf`
+
+Open `/Library/Application\ Support/VMware\ Fusion/vmnet8/dhcpd.conf`. `vmnet8` is the virtual interface for NAT networking in VMWare the guest machines.  In this file, you'll see a subnet clause that looks something like this:
 
 ```
 subnet 172.16.179.0 netmask 255.255.255.0 {
@@ -20,5 +24,9 @@ subnet 172.16.179.0 netmask 255.255.255.0 {
 
 Take note of the line starting with `range`.  The IP addresses you will assign your guest machines will need to fall *outside* that range.
 
+## 3. Update your `/etc/hosts` file to assign your guest machine with a static IP address a fancy hostname.
+
+## 4. Restart the VMWare daemons
+
 * _source_: http://crshlv.ly/rjlXdS
 * _note_: These instructions have been tested on Snow Leopard only.
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -1,13 +1,10 @@
 # How to setup your VMWare Fusion images to use static IP addresses on Mac OS X
 
-* _source_: http://crshlv.ly/rjlXdS
-* _note_: These instructions have been tested on Snow Leopard only.
-
-We use [Railsmachine's](http://railsmachine.com) Moonshine to automate the configuration of our servers at Crush + Lovely.  When writing our deployment recipes, VMWare Fusion's ability to take snapshots and rollback to these snapshots is a huge timesaver because it takes just seconds to roll a server image to it's original state.
+At [Crush + Lovely](http://crushlovely.com), we use [Railsmachine's](http://railsmachine.com) Moonshine to automate the configuration of our servers.  When writing our deployment recipes, VMWare Fusion's ability to take snapshots and rollback to these snapshots is a huge timesaver because it takes just seconds to roll a server image to it's original state.
 
 When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them.
 
-Start by opening `/Library/Application\ Support/VMware\ Fusion/vmnet8/dhcpd.conf`. `vmnet8` is the virtual interface for NAT networking in VMWare the guest machines.  In this file, you'll see a subnet clause that looks something like this:
+Now open `/Library/Application\ Support/VMware\ Fusion/vmnet8/dhcpd.conf`. `vmnet8` is the virtual interface for NAT networking in VMWare the guest machines.  In this file, you'll see a subnet clause that looks something like this:
 
 ```
 subnet 172.16.179.0 netmask 255.255.255.0 {
@@ -22,3 +19,6 @@ subnet 172.16.179.0 netmask 255.255.255.0 {
 ```
 
 Take note of the line starting with `range`.  The IP addresses you will assign your guest machines will need to fall *outside* that range.
+
+* _source_: http://crshlv.ly/rjlXdS
+* _note_: These instructions have been tested on Snow Leopard only.
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -9,7 +9,7 @@ When you're just configuring a single server, having a static IP address for you
 
 Start by opening `/Library/Application\ Support/VMware\ Fusion/vmnet8/dhcpd.conf`. `vmnet8` is the virtual interface for NAT networking in VMWare the guest machines.  In this file, you'll see a subnet clause that looks something like this:
 
-@@@
+```
 subnet 172.16.179.0 netmask 255.255.255.0 {
 	range 172.16.179.128 172.16.179.254;
 	option broadcast-address 172.16.179.255;
@@ -19,6 +19,6 @@ subnet 172.16.179.0 netmask 255.255.255.0 {
 	max-lease-time 7200;                    # default is 2 hours
 	option routers 172.16.179.2;
 }
-@@@
+```
 
 Take note of the line starting with `range`.  The IP addresses you will assign your guest machines will need to fall *outside* that range.
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -7,4 +7,18 @@ We use [Railsmachine's](http://railsmachine.com) Moonshine to automate the confi
 
 When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them.
 
-Start by opening `/Library/Application Support/VMware\ Fusion/vmnet8/dhcpd.conf`. `vmnet8` is the virtual interface for NAT networking in VMWare the guest machines.
+Start by opening `/Library/Application\ Support/VMware\ Fusion/vmnet8/dhcpd.conf`. `vmnet8` is the virtual interface for NAT networking in VMWare the guest machines.  In this file, you'll see a subnet clause that looks something like this:
+
+@@@
+subnet 172.16.179.0 netmask 255.255.255.0 {
+	range 172.16.179.128 172.16.179.254;
+	option broadcast-address 172.16.179.255;
+	option domain-name-servers 172.16.179.2;
+	option domain-name localdomain;
+	default-lease-time 1800;                # default is 30 minutes
+	max-lease-time 7200;                    # default is 2 hours
+	option routers 172.16.179.2;
+}
+@@@
+
+Take note of the line starting with `range`.  The IP addresses you will assign your guest machines will need to fall *outside* that range.
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -1,8 +1,10 @@
-# How to setup your VMWare Fusion images to use static IP addresses
+# How to setup your VMWare Fusion images to use static IP addresses on Mac OS X
 
-_source_: http://crshlv.ly/rjlXdS
+* _source_: http://crshlv.ly/rjlXdS
+* _note_: These instructions have been tested on Snow Leopard only.
 
 We use [Railsmachine's](http://railsmachine.com) Moonshine to automate the configuration of our servers at Crush + Lovely.  When writing our deployment recipes, VMWare Fusion's ability to take snapshots and rollback to these snapshots is a huge timesaver because it takes just seconds to roll a server image to it's original state.
 
 When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them.
 
+Start by opening `/Library/Application Support/VMware\ Fusion/vmnet8/dhcpd.conf`. `vmnet8` is the virtual interface for NAT networking in VMWare the guest machines.
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -1,3 +1,8 @@
 # How to setup your VMWare Fusion images to use static IP addresses
 
-_original source_: http://crshlv.ly/rjlXdS
+_source_: http://crshlv.ly/rjlXdS
+
+We use [Railsmachine's](http://railsmachine.com) Moonshine to automate the configuration of our servers at Crush + Lovely.  When writing our deployment recipes, VMWare Fusion's ability to take snapshots and rollback to these snapshots is a huge timesaver because it takes just seconds to roll a server image to it's original state.
+
+When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them.
+
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -1 +1,3 @@
-# How to setup your VMWare Fusion images to use static IP addresses
+# How to setup your VMWare Fusion images to use static IP addresses
+
+_original source_: http://crshlv.ly/rjlXdS
diff --git a/setup-vmware-image-with-static-IP.markdown b/setup-vmware-image-with-static-IP.markdown
@@ -0,0 +1 @@
+# How to setup your VMWare Fusion images to use static IP addresses
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		# How to setup your VMWare Fusion images to use static IP addresses