The application will now create a clone of the hdd

  Made it so that the we clone the hdd before launching the instance,
  this way we don't have to worry about the drive going away; and
  we can use the same image to create multiple instances. This does
  add a bit to the bootup process, and the drive does need to be
  cloned. Might be interesting to look into COW/Union fs for this type
  of thing.
Merge branch 'master' of github.com:cmars/juju-vbox into mergy

Fixed conflicts. Moving away from hardlinks and insteading cloning the
harddrives. This makes it possiable to start up multiple vm and not
worry about them overriting each other. Or locking up the harddrive.
Would be interesting to see if a FuseFS could be used to make the clone
operation faster. But for now it works. Also, the networking is working,
just that if you want to get out of the Hostonly network, one need to
put a NAT interface on there, and then ssh onto the box and start up the
second interface. What we can do in the future; is to setup the base
image to assume there are two interface it needs to setup instead of
just one.

Conflicts:
	main.go
Small refactor.

I moved the disk clone to the top of the machine creation; and am runing
the clone in a seprate go routine, then waiting for it to complete
before attaching it to the machine. There really isn't a speedup; but at
least things can happen while the disk is being cloned.
Merge pull request #2 from gdey/master

Some Big changes.