Oct 24 2010

Twitter Weekly Updates for 2010-10-24

  • me 2 cya then #
  • letd do denys...so 7 at dennys then? #

Powered by Twitter Tools

Oct 21 2010

me 2 cya then

me 2 cya then
Oct 21 2010

letd do denys…so 7 at dennys…

letd do denys...so 7 at dennys then?
Oct 14 2010

VirtualBox tip: Restore vs Delete Snapshot

Restore snapshot will restore to the state of the snapshot you select.  That makes sense.

Delete snapshot does NOT make sense.  Delete snapshot MERGES the snapshot to its parent shapshot.  (It IS deleted in that it is no longer needed and therefore removed but it really should have been called Merge Snapshot.)

Oct 01 2010

To enable internal networking using DHCP on multiple VirtualBox VMs do this…

VirtualBox rocks.   I needed to setup 3 virtual box machines so that they would have there own little network.  This is a good thing because the other methods had some limitations… with NAT the VMs cannot communicate with each other.  Bridged Networking will work fine but requires that the bridged network adapter be on a real network which for my situation is not always feasible.  Host-only probably WOULD work in this scenario but it more complex. 

Bottom line…internal allows the VMs to communicate while NOT requiring the presence of a real network and without being overly complex. 

To setup do the following…

from the command line setup a DHCP Server for your internal network by using the following command:

VBoxManage dhcpserver add --netname intnet --ip 192.168.100.100 
--netmask 255.255.255.0 --lowerip 192.168.100.101 --upperip 192.168.100.254
--enable

(NOTE – USE TWO HYPHENS (--) FOR THE SWITCHES). 

The switch setting here are pretty obvious.  The ip switch is the ip address that will be assigned to the DHCP server.  The netmask switch is the subnet mask that will be used by the DHCP server and assigned to the clients.  lowerip and upperip is the range of leased addresses issued by the DHCP server.  Enable activates the server. 

That will create a new DHCP server that will start and lease addresses when you start the VMs that you want to be on the internal network.

Next, on each VM you want to be on the internal network, open the network settings and for at least one of the NICs set it to use Internal as the network type.  Notice that the internal network name is already set to intnet (which is the network for which we created the DHCP server.)

Now when you start each vm they will be automatically added to this private internal network and can communicate with each other.

Happy VMing.

Seth