I've just finished up a lot of learning and now have a happy newborn OpenVZ Linux server (coinciding with my newborn niece Audrey ) running five virtual slices. I built it on a server we at work are phasing out after being a SQL 2000 server, so it's a little slow (dual 1.4 xeons. yawn) but has a decent accelerated RAID card and separate mirrors so it's great for virtualized web use. It just needs to serve up tiny blog HTML files, run some light Ruby on Rails code, tiny MySQL, video, basic email, and private SVN source control systems stuff. But because we need some HTTP hosting action pointing securely internally (SVN server) and most all else running public web sites on the DMZ secure switch, there was a bit of wrangling with network configuration to have dedicated nics, firewalls, and secure routes for everything (and be able to administer it internally). By default, it seems to be configured for shared hosting provider situations - the clients can't talk to each other or the host whatsoever, but can all easily get their own IP and NAT passthrough from the host's NIC. So I had to reverse a lot of that through special configuration I manage most of it through the Mac Terminal SSH program and Webmin from the LAN side of our network, which only has access to the 'host' operating system, known as a 'hardware node' because it's not supposed to be running anything besides monitoring and maybe mail relay. All child virtual slices are bridged network-wise on a virtual linux switch on the host (like between MySQL slice and Apache / Lighttpd slices) or have dedicated nics on the DMZ. I mange the children through the host command line ('vzctl enter 105' opens command prompt of child from host.) Above is a snapshot of the Webmin status summary screen of the finished product. I'll expand on some of the solutions I came up with through doing this install and be posting them here soon, and then posting more as I figure out some tricks.