at.

of the openvz code to handle lvm garbage collection.

managed.

* Try much harder to prevent broken VMs from getting left behind.

* Try even harder to prevent left of state (devices, volumes, etc)
  from getting left behind once a VM breaks.

* Store all the assorted bits of state we create in a file so that it
  it can be cleaned up later.

* Watch for "stale" VMs that got left behind, using the UUID, which is
  regenerated each time an experiment is swapped in. Since we now
  store all the state that was associated with the stale VM, we can
  actually tear it down later. To do this by hand:

   node> sudo /usr/local/etc/emulab/mkvnode.pl -c pcvmXXX-YYY

* Lots of changes to signal handling to avoid a common problem case;
  trying to reboot or halt a VM that is still setting up.

directory.

resource locking issue that iptables should deal with, not me!

resource that must be locked, but the version of iptables we run
on the OPENVZ images bail if the lock is taken. STUPID!

existing containter.

This makes us (closer to) consistent all around and we were populating that
latter file incorrectly anyway!  (though it only mattered with the new
sub-boss mechanism.)

can't do this on vhosts running a different distro/version from the guest.

the tb-set-node-os command with a second optional argument; if that is
present, the first arg is the child OS and the second is the parent OS.
We add some new features in ptopgen (OS-parentOSname-childOSname) based
off a new table that maps which child OSes can run on which parents, and
the right desires get added to match.  We setup the reloads in os_setup
along with the parents.  Also needed a new opmode, RELOAD-PCVM, to handle
all this.

For now, users only have to specify that their images can run on pcvms, a
special hack for which type the images can run on.  This makes sense in
general since there is no point conditionalizing childOS loading on
hardware type at the moment, but rather on parentOS.  Hopefully this stuff
wiill mostly work on shared nodes too, although we'll have to be more
aggressive on the client side garbage collecting old frisbee'd images for
long-lived shared hosts.

I only made these changes in libvtop, so assign_wrapper folks are left in
the dark.

Currently, the client side supports frisbee.  Only in openvz for now, and
this probably breaks libvnode_xen.pm.  Also in here are some openvz
improvements, like ability to sniff out which network is the public
control net, and which is the fake virtual control net.

host by port number, which is redirected into the container.

for post-boot global vnode control (i.e., reboot all vnodes).

Watch for containers that are stopped but mounted, and unmount them.

is rebooting. Just when creating.

the root fs of the vnode before it is booted. Did not want to
duplicate this code in the libraries.

Dave's libvnode abstractions for all the heavy lifting. I just
rearranged the furniture a bit. This deprecates vnodectl, mostly.