the same vlan to be on multiple phys devices.

trivial link betweem two VMs on the same phys host. There is no vlan,
but we can fake things enough so that everything looks as it should by
creating a bridge device with no vlan devices in it.

Cut and paste error.  Doesn't matter since the file isn't used.

writing into a file.

so that it can be used for Xen.

openvz.

Also create var/emulab/boot in the guest -- this should make it possible
to boot any fedora-like guest image, even if it hasn't been emulabized.
However, we need to also add support for the debian way of configuring
interfaces...

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.

status for each "image".

:-).

to exist but their LVM volumes are not mounted.  Also make sure to
activate volumes cause they seem to go inactive across reboots.

Also bump the imq device limit down to 64 for now.  I still prefer to
fixup the problems with the 2.6.27 ovz kernel and change the imq setup
there, rather than add dynamic imq device alloc in 2.6.18... but we'll
see.

vnode creation time linear with the number of images (currently there is
only one, although this support allows for different images for vnodes on
the same vhost).  LVM is currently the default, but I left the old code
too.  Right now, the master logical device for each image gets 8GB; the
snapshots each get 1GB for CoW data.  This all needs to be exposed to user
control somehow.

Also made a ton of resources unlimited, not that it has seemed to improve
performance though.

mkextrafs.pl now supports some basic LVM creation stuff.

correct.

in the root context.  Also, give containers CAP_NET_ADMIN so they can
set the per-device txqueuelen via ifconfig.  This may be a bad idea...
but for now it's helpful!

vzconf global lock, and don't release it if the necessary work has
already been done.

Add unmount hook.

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

devices are allocated unti Dave fixes the driver.

Of course, attaching tc filters via IMQ doesn't seem to work inside
openvz...

bootvnodes/vnodesetup/mkX.pl train in favor of my own strawman design for
a more generic form of virt node support.  The strawman is incomplete and
probably wrong in places, but I had to abandon the quest for anything
better for now.  For now, uses same server side stuff as jails.